Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: MauMau <maumau307(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?
Date: 2013-12-10 04:05:07
Message-ID: 20131210040507.GH2119@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2013-12-10 04:18:06 Re: ANALYZE sampling is too good
Previous Message Amit Kapila 2013-12-10 04:02:09 Re: plpgsql_check_function - rebase for 9.3