| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why does logical replication launcher exit with exit code 1? |
| Date: | 2017-08-02 21:47:00 |
| Message-ID: | 20170802214700.6xdw6qmukvt5dssh@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-08-02 22:28:48 | pgsql: Fix pg_dump's errno checking for zlib I/O |
| Previous Message | Tom Lane | 2017-08-02 21:09:10 | Re: Why does logical replication launcher exit with exit code 1? |