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

From Bruce Momjian
Subject Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?
Date
Msg-id 20131210040507.GH2119@momjian.us
Whole thread Raw
In response to Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Tue, Dec 10, 2013 at 08:47:22AM +0800, Craig Ringer wrote:
> On 12/05/2013 11:25 PM, MauMau wrote:
> > Hello,
> > 
> > My customers and colleagues sometimes (or often?) ask about the
> > following message:
> > 
> > FATAL:  the database system is starting up
> 
> I would LOVE that message to do away, forever.
> 
> It's a huge PITA for automated log monitoring, analysis, and alerting.
> 
> The other one I'd personally like to change, but realise is harder to
> actually do, is to separate "ERROR"s caused by obvious user input issues
> from internal ERRORs like not finding the backing file for a relation,
> block read errors, etc.
> 
> String pattern matching is a crude and awful non-solution, especially
> given the way PostgreSQL loves to output messages to the log in whatever
> language and encoding the current database connection is in.

Yes, this is certainly a challenge.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: plpgsql_check_function - rebase for 9.3
Next
From: Claudio Freire
Date:
Subject: Re: ANALYZE sampling is too good