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

Re: Too much logging

From: Andreas Schmitz <mailinglist(at)longimanus(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Too much logging
Date: 2010-08-27 13:06:20
Message-ID: 4C77B84C.5070507@longimanus.net (view raw or flat)
Thread:
Lists: pgsql-general
http://www.postgresql.org/docs/8.4/interactive/runtime-config-logging.html#GUC-LOG-STATEMENT


[...]

Valid values are none, ddl, mod, and all.


regards

andreas


On 08/27/2010 03:01 PM, Richard Harley wrote:
>
> Won't log state = all catch everything?
>
> Richard
>
> On 27/08/10 10:39, Mike Christensen wrote:
>> Hi all -
>>
>> I've noticed my log files for Postgres are getting way too big, since
>> every single SQL statement being run ends up in the log.  However,
>> nothing I change in postgresql.conf seems to make a bit of
>> difference..  I've tried restarting postgres, deleting all the
>> existing logs, etc.  No matter what I do, every statement is logged.
>>
>> What I want is to only log SQL statements that result in errors.
>> Here's my config options:
>>
>> log_destination = 'stderr'
>> logging_collector = on
>> client_min_messages = error
>> log_min_messages = error
>> log_error_verbosity = default
>> log_min_error_statement = error
>> log_min_duration_statement = 3000
>> log_statement = 'all'
>>
>> Pretty much everything else log related is commented out..  What am I
>> doing wrong?  Thanks!
>>
>> Mike
>>
>
>


In response to

pgsql-general by date

Next:From: Vyacheslav KalininDate: 2010-08-27 13:41:20
Subject: Scalar subquery
Previous:From: Richard HarleyDate: 2010-08-27 13:01:39
Subject: Re: Too much logging

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