Alvaro Herrera <[EMAIL PROTECTED]> writes: > Is there any reason why HeapTupleSatisfiesUpdate return codes are not an > enum, like they are for HeapTupleSatisfiesVacuum?
Advertising
History only (the enum result convention for HeapTupleSatisfiesVacuum is
much younger code, IIRC). Seems like a reasonable change to me.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
