Re: PGStatement#setPrepareThreshold - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: PGStatement#setPrepareThreshold
Date
Msg-id EB097C2E-F660-4857-AFFF-D998AD5C82FF@fastcrypt.com
Whole thread Raw
In response to Re: PGStatement#setPrepareThreshold  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: PGStatement#setPrepareThreshold  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: PGStatement#setPrepareThreshold  (Bruce Momjian <bruce@momjian.us>)
List pgsql-jdbc
On 3-Aug-06, at 6:14 PM, Oliver Jowett wrote:

> Dave Cramer wrote:
>
>> If that's the case then the driver is not doing what it's supposed
>> to be doing. It should be using the named portal (S_3) to do the
>> insert.
>
> No, the driver is fine. It is using a named statement (S_3) but an
> unnamed portal (because it is going to fetch all the data in one go
> and doesn't need to retain the portal after execution)
>
> If your query met the conditions for using a portal-based
> ResultSet, you'd see it use a named portal as well as a named
> statement.

Thanks for clarifying that Oliver, the logs are still misleading in
that they don't name the statement used in the bind message.

--dc--
>
> -O
>


pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: PGStatement#setPrepareThreshold
Next
From: Tom Lane
Date:
Subject: Re: PGStatement#setPrepareThreshold