| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Stanier <alexander(dot)stanier(at)egsgroup(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Change in logging behaviour between 8.1 and 8.2 |
| Date: | 2008-10-24 23:56:01 |
| Message-ID: | 6092.1224892561@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Alexander Stanier <alexander(dot)stanier(at)egsgroup(dot)com> writes:
> We have the following parameters in our postgresql.conf:
> log_min_duration_statement = 10000
> log_duration = on
> log_statement = 'all'
> In PostgreSQL 8.2, it seems the statement and duration are no longer
> logged together (i.e. not on the same log line) which means that you
> can't easily decipher those durations/statements which have been logged
> by log_duration/log_statement from those that have been logged by
> log_min_duration_statement. The fact that they were on one line made
> them very easy to pull out of the logs.
> Was this change intentional?
Yes. People complained about double logging of the full statement text.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-10-25 02:43:44 | Re: pgadmin not processing scheduled jobs |
| Previous Message | Robert Young | 2008-10-24 21:00:00 | Re: pgadmin not processing scheduled jobs |