| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Dave Cramer" <pg(at)fastcrypt(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extended protocol logging |
| Date: | 2006-11-01 15:06:49 |
| Message-ID: | 19138.1162393609@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> On Tue, 2006-10-31 at 23:51 -0500, Tom Lane wrote:
>> With what logging settings? log_duration has rather different behavior
>> from what it used to do.
> I think it would be useful to have the log results from a test program
> in the protocol section,
The contents of the postmaster log are surely not part of the FE protocol.
Clients can't even see the log without resorting to nonstandard hacks.
What it sounds like to me is that Dave's client has got log_duration = ON
when what he should have is log_min_duration_statement = 0. Those two
settings used to be just about redundant but as of 8.2 they have got
distinct functionality. See this thread:
http://archives.postgresql.org/pgsql-hackers/2006-09/msg00681.php
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | korryd | 2006-11-01 15:58:52 | [Fwd: pg_migrator: in-place upgrade tool at pgFoundry] |
| Previous Message | Joshua D. Drake | 2006-11-01 14:56:19 | Re: [HACKERS] Index greater than 8k |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-01 17:05:25 | Re: Writing WAL for relcache invalidation: pg_internal.init |
| Previous Message | Tom Lane | 2006-11-01 14:50:56 | Re: [HACKERS] WAL logging freezing |