Re: [HACKERS] Why does logical replication launcher exit with exitcode 1? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Why does logical replication launcher exit with exitcode 1?
Date
Msg-id 20170802214700.6xdw6qmukvt5dssh@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Why does logical replication launcher exit with exit code 1?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2017-08-02 17:09:10 -0400, Tom Lane wrote:
> Even if we fix that, though, I think it is reasonable to downgrade it to
> DEBUG1.  We did that already for other standard background processes such
> as the autovac launcher, and it's not apparent to me why the logrep
> launcher should be chattier.  Now, *unexpected* starts or stops should
> certainly deserve a higher log rating ... but the general rule ought to be
> that totally-expected behavior does not deserve a log entry by default.

Well, every exit *other* than during a shutdown is unexpected.  That's
why I suggested changing the log level for exit code 1 depending on the
cluster being shut down or not.

- Andres



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Why does logical replication launcher exit with exit code 1?
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] [patch] pg_dump/pg_restore zerror() and strerror()mishap