Postgres Pro
Downloads
Home   >   mailing lists

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

From Fujii Masao
Subject Re: setLastTid() and currtid()
Date
Msg-id CAHGQGwHG6-mBN+Gj3LHq5TAKDxwLZ0yHNC6JUSaxyO8Eo5nTww@mail.gmail.com
Whole thread Raw
In response to Re: setLastTid() and currtid()  (Michael Paquier <michael@paquier.xyz>)
Responses Re: setLastTid() and currtid()  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Tree view 
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?

Regards,

-- 
Fujii Masao

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: In PG12, query with float calculations is slower than PG11
Next
From: Kasahara Tatsuhito
Date:
Subject: Re: Tid scan increments value of pg_stat_all_tables.seq_scan. (butnot seq_tup_read)