Re: pg_receivewal and SIGTERM

From: Christoph Berg <myon(at)debian(dot)org>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_receivewal and SIGTERM
Date: 2022-08-19 10:54:34
Message-ID: Yv9r6s815aba836p@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2022-08-19 11:11:35 Re: logical decoding and replication of sequences, take 2
Previous Message Amit Kapila 2022-08-19 09:54:56 Re: Perform streaming logical transactions by background workers and parallel apply