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

From Tom Lane
Subject Re: setLastTid() and currtid()
Date
Msg-id 21495.1555003623@sss.pgh.pa.us
Whole thread Raw
In response to Re: setLastTid() and currtid()  (Andres Freund <andres@anarazel.de>)
Responses Re: setLastTid() and currtid()
Re: setLastTid() and currtid()
Re: setLastTid() and currtid()
Re: setLastTid() and currtid()
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2019-03-27 10:01:08 +0900, Inoue, Hiroshi wrote:
>> The above code remains only for PG servers whose version < 8.2.
>> Please remove the code around setLastTid().

> Does anybody else have concerns about removing this interface? Does
> anybody think we should have a deprecation phase? Should we remove this
> in 12 or 13?

I think removing it after feature freeze is not something to do,
but +1 for nuking it as soon as the v13 branch opens.  Unless
there's some important reason we need it to be gone in v12?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: cache lookup failed for collation 0
Next
From: Anastasia Lubennikova
Date:
Subject: Re: block-level incremental backup