Re: pg_receivewal and SIGTERM
От | Christoph Berg |
---|---|
Тема | Re: pg_receivewal and SIGTERM |
Дата | |
Msg-id | Yv9r6s815aba836p@msg.df7cb.de обсуждение исходный текст |
Ответ на | Re: pg_receivewal and SIGTERM (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>) |
Ответы |
Re: pg_receivewal and SIGTERM
|
Список | pgsql-hackers |
Re: Bharath Rupireddy > <application>pg_receivewal</application> will exit with status 0 when > - terminated by the <systemitem>SIGINT</systemitem> signal. (That is the > + terminated by the <systemitem>SIGINT</systemitem> or > + <systemitem>SIGTERM</systemitem> signal. (That is the > normal way to end it. Hence it is not an error.) For fatal errors or > other signals, the exit status will be nonzero. > > Can we specify the reason in the docs why a SIGTERM causes (which > typically would cause a program to end with non-zero exit code) > pg_receivewal and pg_recvlogical exit with zero exit code? Having this > in the commit message would help developers but the documentation will > help users out there. We could add "because you want that if it's running as a daemon", but TBH, I'd rather remove the parentheses part. It sounds too much like "it works that way because that way is the sane way". Christoph
В списке pgsql-hackers по дате отправления: