| From: | Richard Harley <richard(at)scholarpack(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Too much logging |
| Date: | 2010-08-27 13:01:39 |
| Message-ID: | 4C77B733.4060701@scholarpack.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Schmitz | 2010-08-27 13:06:20 | Re: Too much logging |
| Previous Message | Richard Harley | 2010-08-27 10:43:05 | Re: Is your data okay? |