| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(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 14:34:05 |
| Message-ID: | AANLkTim559wG-7FvtZ5cSBaqZ9qKoRgDrXkon8c_MURX@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 14, 2010 at 10:30 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Mon, Jun 14, 2010 at 10:08 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> The correct log level for this message is LOG. End of discussion.
>
>> Why?
>
> Because it's not being issued in a user's session. The only place it
> can go is to the system log, and if you use a level of WARNING or less,
> it's likely to get filtered out by log_min_messages.
>
> I'm totally unimpressed by the argument that log-filtering applications
> don't know enough to pay attention to LOG messages. There are already a
> lot of those that are quite important to notice.
I'm willing to buy the above, but nobody has explained to my
satisfaction why it's remotely sane to go into an infinite retry loop
on an unrecoverable error.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-06-14 14:37:08 | Re: Typo in plperl doc ? |
| Previous Message | Tom Lane | 2010-06-14 14:30:00 | Re: warning message in standby |