Re: warning message in standby

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: warning message in standby
Date: 2010-06-14 14:56:38
Message-ID: 1276527398.23257.52164.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2010-06-14 at 10:30 -0400, Tom Lane wrote:

> I'm totally unimpressed by the argument that log-filtering
> applications don't know enough to pay attention to LOG messages.
> There are already a lot of those that are quite important to notice.

We have a log level where 1 log entry in a million is something serious
and all the rest are generally ignorable. That situation leads to the
cognitive phenomena is known as "normalization of deviance", a term
coined in the wake of the Challenger disaster.

Should I be downgrading Hot Standby breakages to LOG? That will
certainly help high availability as well.

--
Simon Riggs www.2ndQuadrant.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-06-14 14:57:08 Re: warning message in standby
Previous Message Greg Sabino Mullane 2010-06-14 14:55:44 Re: Typo in plperl doc ?