Hackers,

Is there any reason why HeapTupleSatisfiesUpdate return codes are not an
enum, like they are for HeapTupleSatisfiesVacuum?

I tried and came up with this patch. If there are no objections, please
apply.

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"El día que dejes de cambiar dejarás de vivir"


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> Is there any reason why HeapTupleSatisfiesUpdate return codes are not an
> enum, like they are for HeapTupleSatisfiesVacuum?

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

Alvaro Herrera wrote:
> Is there any reason why HeapTupleSatisfiesUpdate return codes are not an
> enum, like they are for HeapTupleSatisfiesVacuum?

Applied, thanks.

-Neil

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly