Re: Extended protocol logging

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extended protocol logging
Date: 2006-11-01 12:01:48
Message-ID: 27F12005-DB72-4FE2-AED7-37E865AC7C5D@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


On 31-Oct-06, at 11:51 PM, Tom Lane wrote:

> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>> These are logs from Beta 2.
>
> With what logging settings? log_duration has rather different
> behavior
> from what it used to do.

to be honest I don't know, and looking at the logs I suspect that
this is just logging duration, however it's still looking pretty
ambiguous. ( I will get the settings, my client is on the other side
of the world)

what exactly does it mean ? The total operation was 4.365ms and the
parse was .672 and bind was .128? Is it possible for different
connections to be interleaved? I still think having the parse,
bind,execute show the statement name makes sense if for no other
reason than clarity. I would think writing a log parser would be
fairly challenging without them.

Dave
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2006-11-01 12:02:53 Re: Extended protocol logging
Previous Message Simon Riggs 2006-11-01 11:18:17 Re: Extended protocol logging

Browse pgsql-patches by date

  From Date Subject
Next Message Dave Cramer 2006-11-01 12:02:53 Re: Extended protocol logging
Previous Message Simon Riggs 2006-11-01 11:18:17 Re: Extended protocol logging