Skip site navigation (1) Skip section navigation (2)

Re: [ BUG in logs]

From: Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)ar>
To: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
Cc: Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [ BUG in logs]
Date: 2006-04-11 22:18:24
Message-ID: 4931d75548221952bc28edcadbbdb5a6@localhost (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
OK, you're right about the log_min_error_statement value, but this behaviour has changed from 8.0. In earlier versions ERROR statements did get logged if log_statment was set to all or in 7.4, set to "on" DMaybe I missed something in the changelog of 8.1?

On Tue, 11 Apr 2006 23:51:51 +0200, "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> wrote:
>> From: Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)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        |       '@' || '';
Universidad Nacional        |   DBA, Programador, 
    del Litoral             |   Administrador

In response to


pgsql-bugs by date

Next:From: Peter BrantDate: 2006-04-11 22:59:13
Subject: Re: right sibling is not next child
Previous:From: Guillaume SmetDate: 2006-04-11 21:51:51
Subject: Re: [ BUG in logs]

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group