From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Dorne <kevin(at)catalyst(dot)net(dot)nz>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Printing query durations |
Date: | 2006-03-28 03:34:24 |
Message-ID: | 6D679D26-292B-4F63-A53F-0CF37AD917D2@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 27-Mar-06, at 10:19 PM, Tom Lane wrote:
> Dave Cramer <pg(at)fastcrypt(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Dorne | 2006-03-28 04:33:52 | Re: Printing query durations |
Previous Message | Dave Cramer | 2006-03-28 03:32:28 | Re: gcj has a lot of complaints about 8.1-405 release |