Skip site navigation (1) Skip section navigation (2)

Re: JDBC, prepared queries, and partitioning

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 21:26:45
Message-ID: 1202938005.16770.514.camel@ebony.site (view raw or flat)
Thread:
Lists: pgsql-jdbc
On Wed, 2008-02-13 at 16:06 -0500, Kris Jurka wrote:
> 
> On Wed, 13 Feb 2008, Simon Riggs wrote:
> 
> > On Wed, 2008-02-13 at 15:43 -0500, Kris Jurka wrote:
> >
> >> No, in V3 all prepared statements are prepared regardless of the
> >> threshold.
> >
> > Am I reading the wrong documentation?
> > http://jdbc.postgresql.org/documentation/83/connect.html#connection-parameters
> >
> 
> The documentation is just simplifying the complexities of named vs unnamed 
> statements.  Aside from a couple of exceptions, an unnamed prepared 
> statement should perform equivalently to direct execution of the literal 
> query.  Describing it as semi-prepared is complicated and not particularly 
> useful if there is no way to get non-prepared behavior.

OK, but AFAICS the docs relating to prepareThreshold are wrong. They
describe behaviour that doesn't happen all of the time, yet there is
nothing to indicate that.

Happy to provide a patch, if you'd like.

-- 
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com 


In response to

Responses

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2008-02-13 21:41:26
Subject: Re: JDBC, prepared queries, and partitioning
Previous:From: Simon RiggsDate: 2008-02-13 21:13:42
Subject: Re: JDBC, prepared queries, and partitioning

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group