Re: Slow query after upgrades

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Oliver Jowett" <oliver(at)opencloud(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tom Duffey" <tduffey(at)techbydesign(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Slow query after upgrades
Date: 2007-12-14 00:27:23
Message-ID: 1d4e0c10712131627q7cc8cccdv4494cd6c69c0bc13@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Dec 14, 2007 12:54 AM, Oliver Jowett <oliver(at)opencloud(dot)com> wrote:
> The JDBC driver is using an unnamed statement in this case, shouldn't
> the planner end up using index selectivity estimates based on the actual
> parameter values?

Tom fixed that during the 8.3 development cycle IIRC but it was not
the case in 8.2 and earlier.

--
Guillaume

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Ken Johanson 2007-12-14 00:48:31 Re: RETURNING clause: how to specifiy column indexes?
Previous Message Tom Duffey 2007-12-14 00:19:03 Re: Slow query after upgrades