Re: Too much logging
От | Andreas Schmitz |
---|---|
Тема | Re: Too much logging |
Дата | |
Msg-id | 4C77B84C.5070507@longimanus.net обсуждение исходный текст |
Ответ на | Re: Too much logging (Richard Harley <richard@scholarpack.com>) |
Список | 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 >> > >
В списке pgsql-general по дате отправления: