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

From Magnus Hagander
Subject Re: warning message in standby
Date
Msg-id AANLkTin-AhqF2lEyb-RjSC4HeHAB7DORgZ3pfrWgs8iJ@mail.gmail.com
Whole thread Raw
In response to Re: warning message in standby  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jun 14, 2010 at 20:22, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> LOG is already over-used and so anything said at that level is drowned.
>
> This is nonsense.

Whether it's over-used or not may be, but that doesn't make the
general issue nonsense.

But the fact is that having LOG at a higher priority than WARNING and
ERROR is un-intuitive in the extreme, and I bet there aren't many
non-experts who realize this. I don't know of any other software that
does this. Heck, *experienced* postgresql users keep getting this
wrong. Perhaps we need to re-think the naming there?

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: warning message in standby
Next
From: Joe Conway
Date:
Subject: Re: dblink_build_sql_update versus dropped columns