From: Merlin Moncure <mmoncure@gmail.com>
To: Bucky Jordan <bjordan@lumeta.com>
Cc: Rohit_Behl <Rohit_Behl@infosys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Jdbc/postgres performance
Date: Wed, 18 Oct 2006 09:11:40 +0530
Message-ID: <b42b73150610172041rf8ffb96n3d82cc191815370@mail.gmail.com> (raw)
In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4209D1C@MAIL.corp.lumeta.com>
References: <b42b73150610171328r508ab94dmd70dac6ed78474aa@mail.gmail.com>
<78ED28FACE63744386D68D8A9D1CF5D4209D1C@MAIL.corp.lumeta.com>
On 10/18/06, Bucky Jordan <bjordan@lumeta.com> wrote:
> > On 10/17/06, Rohit_Behl <Rohit_Behl@infosys.com> wrote:
> > > Select events.event_id, ctrl.real_name, events.tsds, events.value,
> > events.lds, events.correction, ctrl.type, ctrl.freq from table events,
> > iso_midw_control ctrl where events.obj_id = ctrl.obj_id and
> > events.event_id > ?::bigint order by events.event_id limit ?
> >
> After a quick search on the JDBC list, it looks like there's some recent
> discussion on the subject of how to give the planner better insight for
> prepared statements (the subject is "Blind Message" if you're
> looking...).
>
> So, I'm off to go read there and perhaps join the jdbc mailing list too.
this is not really a jdbc issue, just a practical problem with
prepared statements...except for the mechanism if any the jdbc driver
allows you to choose if a statement is prepared.
> But, a more general postgres question. I assume if I want to turn
> prepared statements off altogether (say I'm using a jdbc abstraction
you turn off prepared statements by not invoking sql prepare or
PQprepare. (or, if jdbc implements its own protocol client, it's
version of PQprepare).
> layer that likes parameterized statements, and there's other benefits to
> parameterizing other than just saving on db parse/plan) can I set
> max_prepared_transactions to 0? Is there any other option outside of
this setting is for 2pc and is not relevent to the discussion :) even
if it were, im not so sure about a setting designed to enforce a
partcular method of querying.
yes, you are correct this is not exactly the use case for hints being
discussed in -hackers. however, imho, this is much more important and
relevant so long as prepared statements continue to work the way they
do.
merlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mmoncure@gmail.com, bjordan@lumeta.com, Rohit_Behl@infosys.com
Subject: Re: Jdbc/postgres performance
In-Reply-To: <b42b73150610172041rf8ffb96n3d82cc191815370@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox