| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 17:20:26 |
| Message-ID: | 1162401626.3587.133.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Wed, 2006-11-01 at 10:06 -0500, Tom Lane wrote:
> "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.
OK, can we please put the example from -hackers into the docs,
somewhere, with particular note of which protocol messages result in
which logging output?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-11-01 18:15:42 | Re: Writing WAL for relcache invalidation:pg_internal.init |
| Previous Message | Tom Lane | 2006-11-01 17:05:25 | Re: Writing WAL for relcache invalidation: pg_internal.init |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-11-01 18:15:42 | Re: Writing WAL for relcache invalidation:pg_internal.init |
| Previous Message | Tom Lane | 2006-11-01 17:05:25 | Re: Writing WAL for relcache invalidation: pg_internal.init |