From: | "MauMau" <maumau307(at)gmail(dot)com> |
---|---|
To: | "David Johnston" <polobo(at)yahoo(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [RFC] Shouldn't we remove annoying FATAL messages from server log? |
Date: | 2013-12-07 11:50:48 |
Message-ID: | 5A120D22826D49839B1C7104B899EC37@maumau |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: "David Johnston" <polobo(at)yahoo(dot)com>
>> 5. FATAL: terminating walreceiver process due to administrator command
>> 6. FATAL: terminating background worker \"%s\" due to administrator
>> command
> 5 and 6: I don't fully understand when they would happen but likely fall
> into the same "the DBA should know what is going on with their server and
> confirm any startup/shutdown activity it is involved with".
>
> They might be better categorized "NOTICE" level if they were in response
> to
> a administrator action, versus in response to a crashed process, but even
> for the user-initiated situation making sure they hit the log but using
> FATAL is totally understandable and IMO desirable.
#5 is output when the DBA shuts down the replication standby server.
#6 is output when the DBA shuts down the server if he is using any custom
background worker.
These messages are always output. What I'm seeing as a problem is that
FATAL messages are output in a normal situation, which worries the DBA, and
those messages don't help the DBA with anything. They merely worry the DBA.
Regards
MauMau
From | Date | Subject | |
---|---|---|---|
Next Message | MauMau | 2013-12-07 12:18:38 | Re: Re: [RFC] Shouldn't we remove annoying FATAL messages from server log? |
Previous Message | Jeff Davis | 2013-12-07 08:12:40 | Re: Extension Templates S03E11 |