Re: BUG #1753: Query Optimizer does not work well with libpg

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Ernst Bachmann <e(dot)bachmann(at)xebec(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1753: Query Optimizer does not work well with libpg
Date: 2005-07-05 23:16:40
Message-ID: 42CB14D8.9020504@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ernst Bachmann wrote:
> The following bug has been logged online:
>
> Bug reference: 1753
> Logged by: Ernst Bachmann
> Email address: e(dot)bachmann(at)xebec(dot)de
> PostgreSQL version: 8.0.3
> Operating system: Linux
> Description: Query Optimizer does not work well with libpg /
> PQexecParams
> Details:
>
> It looks like the query optimizer isn't taking the value of parameters sent
> with PQexecParams into account, thus generating (in my case, very) unoptimal
> plans

If PQexecParams uses the unnamed statement (it appears to), this
shouldn't happen -- planning of the unnamed statement is delayed until
the first set of parameter values is bound. This behaviour started in 8.0.

What's the query?

Are you definitely using PQexecParams() and not PQexecPrepared()?

-O

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew - Supernews 2005-07-06 00:03:01 Re: BUG #1753: Query Optimizer does not work well with libpg
Previous Message Tom Lane 2005-07-05 21:12:28 Re: bug: core dump in pl/perl (cvs head).