Postgres Pro
Downloads
Home   >   mailing lists

Re: Removal of currtid()/currtid2() and some table AM cleanup - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Removal of currtid()/currtid2() and some table AM cleanup
Date
Msg-id 1304031.1605891191@sss.pgh.pa.us
Whole thread Raw
In response to Re: Removal of currtid()/currtid2() and some table AM cleanup  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Removal of currtid()/currtid2() and some table AM cleanup  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> On 2020-09-03 12:14, Michael Paquier wrote:
>> Opinions are welcome about the arguments of upthread.

> It appears that currtid2() is still used, so we ought to keep it.

Yeah, if pgODBC were not using it at all then I think it'd be fine
to get rid of, but if it still contains calls then we cannot.
The suggestion upthread that those calls might be unreachable
is interesting, but it seems unproven.

            regards, tom lane

pgsql-hackers by date:

Previous
From: James Coleman
Date:
Subject: Re: enable_incremental_sort changes query behavior
Next
From: Robert Haas
Date:
Subject: Re: enable_incremental_sort changes query behavior