Re: setLastTid() and currtid()

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: setLastTid() and currtid()
Дата
Msg-id 21495.1555003623@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: setLastTid() and currtid()  (Andres Freund <andres@anarazel.de>)
Ответы Re: setLastTid() and currtid()  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: setLastTid() and currtid()  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: setLastTid() and currtid()  (Andres Freund <andres@anarazel.de>)
Re: setLastTid() and currtid()  (Andres Freund <andres@anarazel.de>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: cache lookup failed for collation 0
Следующее
От: Anastasia Lubennikova
Дата:
Сообщение: Re: block-level incremental backup