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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers