Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I'm thinking that I'll to add a new elog level to signal a can't-happen
> condition within the transaction machinery, which would abort the whole
> transaction tree (more than ERROR) but would not take the whole backend
> down (less than FATAL).  What should it be called?  Do people agree that
> it's needed?

If you think it's just for can't-happen conditions, FATAL (or even Assert)
should cover it.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to