Re: PGStatement#setPrepareThreshold

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: PGStatement#setPrepareThreshold
Date: 2006-08-03 22:20:47
Message-ID: EB097C2E-F660-4857-AFFF-D998AD5C82FF@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tom Lane 2006-08-03 22:49:00 Re: PGStatement#setPrepareThreshold
Previous Message Oliver Jowett 2006-08-03 22:14:48 Re: PGStatement#setPrepareThreshold