Re: HeapTupleSatisfiesUpdate result as enum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: HeapTupleSatisfiesUpdate result as enum
Date: 2005-03-19 16:17:07
Message-ID: 15852.1111249027@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)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

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-03-19 19:09:53 Re: Shared dependency patch
Previous Message Alvaro Herrera 2005-03-19 06:07:42 HeapTupleSatisfiesUpdate result as enum