Search Postgresql Archives

Re: Too much logging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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





--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux