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 1547394.1605982415@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  (Andres Freund <andres@anarazel.de>)
Re: Removal of currtid()/currtid2() and some table AM cleanup  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> Indeed, this could go.  There is a recursive call for views, but in
> order to maintain compatibility with that we can just remove one
> function and move the second to use a regclass as argument, like the
> attached, while removing setLastTid().  Any thoughts?

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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Connection using ODBC and SSL
Next
From: Andres Freund
Date:
Subject: Re: Removal of currtid()/currtid2() and some table AM cleanup