Re: [martin@bugs.unl.edu.ar: BUG in logs]
От | Martin Marques |
---|---|
Тема | Re: [martin@bugs.unl.edu.ar: BUG in logs] |
Дата | |
Msg-id | 4931d75548221952bc28edcadbbdb5a6@localhost обсуждение исходный текст |
Ответ на | Re: [martin@bugs.unl.edu.ar: BUG in logs] ("Guillaume Smet" <guillaume.smet@gmail.com>) |
Ответы |
Re: [martin@bugs.unl.edu.ar: BUG in logs]
|
Список | pgsql-bugs |
OK, you're right about the log_min_error_statement value, but this behaviour has changed from 8.0. In earlier versions ERRORstatements did get logged if log_statment was set to all or in 7.4, set to "on" DMaybe I missed something in the changelogof 8.1? On Tue, 11 Apr 2006 23:51:51 +0200, "Guillaume Smet" <guillaume.smet@gmail.com> wrote: >> From: Martin Marques <martin@bugs.unl.edu.ar> >> I encountered a rare BUG in the way PG is logging. Let me first enlight > with some configuration I have and PG version: > > Perhaps I'm missing something but I think it's not a bug but a > configuration problem. > >> log_min_error_statement | panic > > If you set this one to error instead of panic, you will have your > failed statements logged. > >> log_statement | all > > This one only logs successful queries so it's normal you don't have > the statement in the log file if it fails. > > Regards, > > -- --------------------------------------------------------- Lic. MartÃn Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador ---------------------------------------------------------
В списке pgsql-bugs по дате отправления: