Re: setLastTid() and currtid() - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: setLastTid() and currtid()
Date
Msg-id 20201013181253.GG24889@momjian.us
Whole thread Raw
In response to Re: setLastTid() and currtid()  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: setLastTid() and currtid()
List pgsql-hackers
On Fri, Feb  7, 2020 at 05:24:12PM +0900, Fujii Masao wrote:
> On Fri, Apr 12, 2019 at 1:44 PM Michael Paquier <michael@paquier.xyz> wrote:
> >
> > On Thu, Apr 11, 2019 at 02:06:13PM -0400, Tom Lane wrote:
> > > Yeah, if we could simplify the tableam API, that would be sufficient
> > > reason to remove the stuff in v12, IMO.  But if it is outside of that
> > > API, I'd counsel waiting till v13.
> >
> > Yes, I agree that simplifying the table AM interface would be a reason
> > fine enough to delete this code for v12.  If not, v13 sounds better at
> > this stage.
> 
> Now we are in the dev of v13, so it's time to rip the functions out?

Where are we on this?  Can the functions be removed in PG 14?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: lost replication slots after pg_upgrade
Next
From: Russell Foster
Date:
Subject: Re: [Patch] Using Windows groups for SSPI authentication