From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | MauMau <maumau307(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | 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 15:59:53 |
Message-ID: | 1386777593.27517.YahooMailNeo@web162903.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
MauMau <maumau307(at)gmail(dot)com> wrote:
> From: "Kevin Grittner" <kgrittn(at)ymail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-12-11 16:01:13 | Re: Why the buildfarm is all pink |
Previous Message | Tom Lane | 2013-12-11 15:43:00 | Re: Extension Templates S03E11 |