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

From Michael Paquier
Subject Re: setLastTid() and currtid()
Date
Msg-id 20190412044403.GM2144@paquier.xyz
Whole thread Raw
In response to Re: setLastTid() and currtid()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: setLastTid() and currtid()
Re: setLastTid() and currtid()
List pgsql-hackers
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.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Adding Unix domain socket path and port topg_stat_get_wal_senders()
Next
From: Jeevan Chalke
Date:
Subject: Re: cache lookup failed for collation 0