Re: warning message in standby - Mailing list pgsql-hackers

From Robert Haas
Subject Re: warning message in standby
Date
Msg-id AANLkTin4ZYi2HawTzI53uJ0ER3KTR2tVewvqP1MBiUD4@mail.gmail.com
Whole thread Raw
In response to Re: warning message in standby  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: warning message in standby
Re: warning message in standby
Re: warning message in standby
List pgsql-hackers
On Mon, Jun 14, 2010 at 11:09 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> Should I be downgrading Hot Standby breakages to LOG? That will
>> certainly help high availability as well.
>
> If a message is being issued in a non-user-connected session, there
> is basically not a lot of point in WARNING or below.  It should either
> be LOG, or ERROR/FATAL/PANIC (which are probably all about the same
> thing in the startup process...)

I think Simon's point here is the same as mine - LOG isn't too high -
it's too low.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Typo in plperl doc ?
Next
From: "Kevin Grittner"
Date:
Subject: Re: GSoC - Materialized Views - is stale or fresh?