Re: warning message in standby
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Simon Riggs <simon@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Magnus Hagander <magnus@hagander.net>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-06-14T15:14:38Z
Lists: 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