"Tom Lane" <[EMAIL PROTECTED]> writes:
> Heikki Linnakangas <[EMAIL PROTECTED]> 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 O
Heikki Linnakangas <[EMAIL PROTECTED]> 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
"Heikki Linnakangas" <[EMAIL PROTECTED]> 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?
The comments for heap_get_latest_tid() seem to apply. The
Heikki Linnakangas wrote:
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?
If you have a look at the CVS annotations (
http://developer.postgresql.org/cvs
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?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
---(end of broadc
