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 1506173.1605927008@sss.pgh.pa.us
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  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> What about cutting the cake in two and just remove
> currtid() then?

+1.  That'd still let us get rid of setLastTid() which is
the ugliest part of the thing, IMO.

            regards, tom lane



pgsql-hackers by date:

Previous
From: James Coleman
Date:
Subject: Fix generate_useful_gather_paths for parallel unsafe pathkeys
Next
From: Michael Paquier
Date:
Subject: Re: Removal of currtid()/currtid2() and some table AM cleanup