Re: [RFC] Shouldn't we remove annoying FATAL messages from server log? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?
Date
Msg-id 1386777593.27517.YahooMailNeo@web162903.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?  ("MauMau" <maumau307@gmail.com>)
Responses Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?
List pgsql-hackers
MauMau <maumau307@gmail.com> wrote:
> From: "Kevin Grittner" <kgrittn@ymail.com>

> FATAL is used when the problem is severe enough that the process
> or connection must end. It seems to me to be what should
> consistently be used when a client connection or its process must
> be terminated for a reason other than a client-side request to
> terminate.
>
> What do you think of #5 and #6 when matching the above criteria?
>
> 5. FATAL:  terminating walreceiver process due to administrator
> command
> 6. FATAL:  terminating background worker \"%s\" due to
> administrator command

Those are client connections and their backends terminated for a
reason other than the client side of the connection requesting it.
If we don't classify those as FATAL then the definition of FATAL
becomes much more fuzzy.  What would you define it to mean?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Extension Templates S03E11
Next
From: Andres Freund
Date:
Subject: Re: Why the buildfarm is all pink