Re: pg_receivewal and SIGTERM

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: pg_receivewal and SIGTERM
Дата
Msg-id A41680AB-4E4F-4E70-9DDC-30B35ED3017F@yesql.se
обсуждение исходный текст
Ответ на Re: pg_receivewal and SIGTERM  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: pg_receivewal and SIGTERM  (Michael Paquier <michael@paquier.xyz>)
Re: pg_receivewal and SIGTERM  (Christoph Berg <myon@debian.org>)
Список pgsql-hackers
> On 23 Aug 2022, at 02:15, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Mon, Aug 22, 2022 at 04:05:16PM +0200, Christoph Berg wrote:
>> Do you mean it can, or can not be backpatched? (I'd argue for
>> backpatching since the behaviour is slightly broken at the moment.)
>
> I mean that it is fine to backpatch that, in my opinion.

I think this can be argued both for and against backpatching.  Catching SIGTERM
makes a lot of sense, especially given systemd's behavior.  On the other hand,
This adds functionality to something arguably working as intended, regardless
of what one thinks about the intent.

The attached adds the Exit Status section to pg_recvlogical docs which is
present in pg_receivewal to make them more aligned, and tweaks comments to
pgindent standards. This is the version I think is ready to commit.

--
Daniel Gustafsson        https://vmware.com/


Вложения

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

Предыдущее
От: Önder Kalacı
Дата:
Сообщение: Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Следующее
От: vignesh C
Дата:
Сообщение: Re: Column Filtering in Logical Replication