From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: log_duration
Date: Mon, 7 Feb 2005 16:40:39 -0800
Message-ID: <KGEFLMPJFBNNLNOOOPLGCEIMCIAA.simon@2ndquadrant.com> (raw)
In-Reply-To: <4984.1107711157@sss.pgh.pa.us>
>Tom Lane
> "Simon Riggs" <simon@2ndquadrant.com> writes:
> > Further update on this:
>
> > We've isolated this issue to JDBC client access.
>
> Ah-hah, now it makes sense. I believe the JDBC driver always uses
> extended query protocol (parse/bind/execute messages).
Thanks for the *solution.
I had a D'Oh moment about 2 hours after I posted...
> As a quick workaround until someone thinks of a better idea,
> it might be
> sufficient to attach logging code to the execute phase, and ignore the
> partial-execution issue.
Done... we're getting results out now.
I'm logging both duration of execution and the statement text, as would
be displayed in pg_stat_activity.
Thanks,
Best Regards, Simon Riggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: simon@2ndquadrant.com, tgl@sss.pgh.pa.us
Subject: Re: log_duration
In-Reply-To: <KGEFLMPJFBNNLNOOOPLGCEIMCIAA.simon@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox