Re: currtid_byreloid and currtid_byrelname

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: currtid_byreloid and currtid_byrelname
Date: 2007-06-15 23:07:59
Message-ID: 23789.1181948879@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2007-06-15 23:17:23 Re: currtid_byreloid and currtid_byrelname
Previous Message Gregory Stark 2007-06-15 23:05:51 Re: currtid_byreloid and currtid_byrelname