Re: warning message in standby
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, 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:34:29Z
Lists: pgsql-hackers
On Mon, 2010-06-14 at 11:14 -0400, Robert Haas wrote: > 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. Yes, *and* how do we decide which this is? Should I downgrade all of my code to throwing LOGs rather than ERRORs, because (following the same argument) doing so would be better for high availability? It's not a facetious question. -- Simon Riggs www.2ndQuadrant.com