Re: Prepared statement not using an index - Mailing list pgsql-jdbc

From Guido Neitzer
Subject Re: Prepared statement not using an index
Date
Msg-id 0C0329E7-1A4B-478C-A003-5C605496FC19@pharmaline.de
Whole thread Raw
In response to Re: Prepared statement not using an index  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: Prepared statement not using an index  (Jan de Visser <jdevisser@digitalfairway.com>)
List pgsql-jdbc
On 02.09.2005, at 0:52 Uhr, Oliver Jowett wrote:

>> I use PostgreSQL 8.0.3 on Mac OS X and the JDBC driver 8.0-312
>> JDBC 3.
>>
>> After a lot of other things, I tried using a 7.4 driver and with
>> this,
>> the index is used in both cases.
>>
>
> The 8.0 drivers pass parameters individually to the backend (analogous
> to using PREPARE/EXECUTE), while the 7.4 drivers do textual
> substitution
> into the query text. This can result in different query plans as
> you've
> discovered.

This sounds like a bug to me. If a simple substitution of the
placeholders with actual values ends with different query plan, my
understanding is, that there is something broken in the query
planner ...

cug

pgsql-jdbc by date:

Previous
From: Joseph Shraibman
Date:
Subject: Getting vacuum results
Next
From: Martin Taal
Date:
Subject: timestamp moves when setting and getting a value from postgresql