Re: PGStatement#setPrepareThreshold

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: Oliver Jowett <oliver(at)opencloud(dot)com>, 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>
Subject: Re: PGStatement#setPrepareThreshold
Date: 2006-08-04 03:55:02
Message-ID: 200608040355.k743t2e28676@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Dave Cramer wrote:
>
> 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.

Current CVS has:

(errmsg("statement: [protocol] <BIND> %s", portal_name)));

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bruce Momjian 2006-08-04 03:57:53 Re: PGStatement#setPrepareThreshold
Previous Message Tom Lane 2006-08-03 22:49:00 Re: PGStatement#setPrepareThreshold