| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, 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 16:49:30 |
| Message-ID: | AANLkTimciMJnNEfRbt-nko9yAerSyFwD4wg4yZ-WLkC5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 14, 2010 at 12:31 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> If that's the case, I guess Tom's right, once more, saying that LOG is
>> fine here. If we want to be more subtle than that, we'd need to revise
>> each and every error message and attribute it the right level, which it
>> probably have already anyway.
>
> Nobody is arguing with what Tom has said about log levels.
Agreed.
> The problem is that LOG already has many things like performance logging
> which aren't a problem as all. So we need a level between LOG and FATAL
> to draw anyone's attention.
Not sure I agree with this - what I think the problem is here is we
need to make a clear distinction between recoverable errors and
unrecoverable errors.
> @Robert - I'd point out that the behaviour of archive_cleanup_command
> and recovery_end_command is broken as a result of this discussion.
:-(
How so?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-06-14 17:00:09 | Re: warning message in standby |
| Previous Message | Simon Riggs | 2010-06-14 16:31:09 | Re: warning message in standby |