Re: currtid_byreloid and currtid_byrelname - Mailing list pgsql-hackers

From Tom Lane
Subject Re: currtid_byreloid and currtid_byrelname
Date
Msg-id 23789.1181948879@sss.pgh.pa.us
Whole thread Raw
In response to currtid_byreloid and currtid_byrelname  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: currtid_byreloid and currtid_byrelname  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki@enterprisedb.com> writes:
> In utils/adt/tid.c, there's two mysterious functions with no comments, 
> and no-one calling them inside backend code AFAICT: currtid_byreloid and 
> currtid_byrelname. What do they do/did?

IIRC, the ODBC driver uses them, or once did, to deal with
concurrent-update situations --- it wants to be able to find the
currently committed version of a row it saw as valid earlier in the
transaction.  I think it's sort of a client-side version of the
EvalPlanQual stuff.  Hiroshi probably remembers more.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: currtid_byreloid and currtid_byrelname
Next
From: Gregory Stark
Date:
Subject: Re: currtid_byreloid and currtid_byrelname