Re: Removal of currtid()/currtid2() and some table AM cleanup

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Removal of currtid()/currtid2() and some table AM cleanup
Дата
Msg-id 1547394.1605982415@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Removal of currtid()/currtid2() and some table AM cleanup  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Removal of currtid()/currtid2() and some table AM cleanup
Re: Removal of currtid()/currtid2() and some table AM cleanup
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Connection using ODBC and SSL
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Removal of currtid()/currtid2() and some table AM cleanup