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

From Peter Eisentraut
Subject Re: Removal of currtid()/currtid2() and some table AM cleanup
Date
Msg-id 9c80b43e-3090-a343-32d1-ff774de74402@enterprisedb.com
Whole thread Raw
In response to Re: Removal of currtid()/currtid2() and some table AM cleanup  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Removal of currtid()/currtid2() and some table AM cleanup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2020-09-03 12:14, Michael Paquier wrote:
> On Fri, Jun 26, 2020 at 01:11:55PM +0900, Michael Paquier wrote:
>>  From what I can see on this thread, we could just remove currtid() per
>> the arguments of the RETURNING ctid clause supported since PG 8.2, but
>> it would make more sense to me to just remove both currtid/currtid2()
>> at once.
> 
> The CF bot is complaining, so here is a rebase for the main patch.
> Opinions are welcome about the arguments of upthread.

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: abstract Unix-domain sockets
Next
From: Gilles Darold
Date:
Subject: Re: Issue with server side statement-level rollback