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

From Michael Paquier
Subject Re: Removal of currtid()/currtid2() and some table AM cleanup
Date
Msg-id 20201122020932.GA1651@paquier.xyz
Whole thread Raw
In response to Re: Removal of currtid()/currtid2() and some table AM cleanup  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Removal of currtid()/currtid2() and some table AM cleanup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Nov 21, 2020 at 01:13:35PM -0500, Tom Lane wrote:
> Considering that we're preserving this only for backwards compatibility,
> I doubt that changing the signature is a good idea.  It maybe risks
> breaking something, and the ODBC driver is hardly going to notice
> any improved ease-of-use.

So, what you are basically saying is to switch currtid_byreloid() to
become a function local to tid.c.  And then have just
currtid_byrelname() and currtid_for_view() call that, right?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Covering SPGiST index
Next
From: Andy Fan
Date:
Subject: Re: Different results between PostgreSQL and Oracle for "for update" statement