Re: Printing query durations - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Printing query durations
Date
Msg-id 6D679D26-292B-4F63-A53F-0CF37AD917D2@fastcrypt.com
Whole thread Raw
In response to Re: Printing query durations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc
On 27-Mar-06, at 10:19 PM, Tom Lane wrote:

> Dave Cramer <pg@fastcrypt.com> writes:
>> There is no difference between a jdbc query and a psql query. The
>> backend doesn't know where the query comes from.
>
> However, the backend has different code paths for V2 and V3 protocol,
> and it could be that what he's looking at is a deficiency in the V3
> protocol logging support.  If so, telling jdbc to use V2 would help.
> (I'm being tentative about this because the backend version was not
> mentioned --- we've fixed some of that stuff in recent releases.)

AFAIR, the deficiencies are in the logging of the prepared
statements. Duration should be logged regardless, no ?
>
>             regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>                http://archives.postgresql.org
>


pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: gcj has a lot of complaints about 8.1-405 release
Next
From: Kevin Dorne
Date:
Subject: Re: Printing query durations