Re: Upper limit arguments of pg_logical_slot_xxx_changes functionsaccept invalid values

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Upper limit arguments of pg_logical_slot_xxx_changes functionsaccept invalid values
Дата
Msg-id 20181002044938.GT11712@paquier.xyz
обсуждение исходный текст
Ответ на Re: Upper limit arguments of pg_logical_slot_xxx_changes functionsaccept invalid values  (Masahiko Sawada <sawada.mshk@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
On Tue, Aug 14, 2018 at 10:00:49AM +0900, Masahiko Sawada wrote:
> I might be missing something but I think the setting either 0 or
> negative values to it solves this problem. Since the upto_nchanges is
> int32 we cannot build if somebody reverted
> 0ab9d1c4b31622e9176472b4276f3e9831e3d6ba.

I don't link that we should change the existing behavior either which is
here for a couple of releases already, so let's mark the patch as
returned with feedback.
--
Michael
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [PATCH] get rid of StdRdOptions, use individual binaryreloptions representation for each relation kind instead
Следующее
От: Etsuro Fujita
Дата:
Сообщение: Re: de-deduplicate code in DML execution hooks in postgres_fdw