Re: HeapTupleSatisfiesUpdate result as enum

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