From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL - JDBC <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBC, prepared queries, and partitioning |
Date: | 2008-02-13 23:13:26 |
Message-ID: | 1202944406.16770.562.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Wed, 2008-02-13 at 17:47 -0500, Kris Jurka wrote:
>
> On Wed, 13 Feb 2008, Simon Riggs wrote:
>
> > But the code example shows explicit use of
> >
> > pgconn.setPrepareThreshold(5);
> >
> > which clearly does nothing, given the default setting of protocol V3.
> >
> > So the program shown only works as stated with 7.3, the last time the
> > default connection protocol was v2.
>
> No, you've got it all backwards. prepareThreshold only does something
> with V3.
OK. I was confused by your statement that "in V3 all prepared statements
are prepared regardless of the threshold". I took that to mean that the
prepareThreshold did nothing at all in V3, which threw everything I
understood on its head.
Many thanks for clarifications from yourself and Oliver.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-02-13 23:19:12 | Re: JDBC, prepared queries, and partitioning |
Previous Message | Oliver Jowett | 2008-02-13 22:57:01 | Re: JDBC, prepared queries, and partitioning |