From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | 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 00:47:22 |
Message-ID: | 52A6649A.9020306@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2013-12-10 00:53:19 | Re: ANALYZE sampling is too good |
Previous Message | Tom Lane | 2013-12-10 00:26:00 | Re: [RFC] Shouldn't we remove annoying FATAL messages from server log? |