| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, 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 18:35:06 |
| Message-ID: | AANLkTin-AhqF2lEyb-RjSC4HeHAB7DORgZ3pfrWgs8iJ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 14, 2010 at 20:22, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)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 Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2010-06-14 18:47:26 | Re: dblink_build_sql_update versus dropped columns |
| Previous Message | Josh Berkus | 2010-06-14 18:32:24 | Re: warning message in standby |