| From: | "MauMau" <maumau307(at)gmail(dot)com> |
|---|---|
| To: | "Andres Freund" <andres(at)2ndquadrant(dot)com> |
| Cc: | "Kevin Grittner" <kgrittn(at)ymail(dot)com>, "Greg Stark" <stark(at)mit(dot)edu>, "David Johnston" <polobo(at)yahoo(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [RFC] Shouldn't we remove annoying FATAL messages from server log? |
| Date: | 2013-12-11 17:04:34 |
| Message-ID: | F32FC143969F434D826FA0A7FADA0D3F@maumau |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: "Andres Freund" <andres(at)2ndquadrant(dot)com>
> On 2013-12-12 00:31:25 +0900, MauMau wrote:
>> 5. FATAL: terminating walreceiver process due to administrator command
>> 6. FATAL: terminating background worker \"%s\" due to administrator
>> command
>
> Those are important if they happen outside a shutdown. So, if you really
> want to remove them from there, you'd need to change the signalling to
> handle the cases differently.
How are they important? If someone mistakenly sends SIGTERM to walreceiver
and background workers, they are automatically launched by postmaster or
startup process later like other background processes. But other background
processes such as walsender, bgwriter, etc. don't emit FATAL messages.
Regards
MauMau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-12-11 17:09:58 | Re: Why the buildfarm is all pink |
| Previous Message | Alvaro Herrera | 2013-12-11 17:00:05 | Re: pgsql: Fix a couple of bugs in MultiXactId freezing |