Re: Poor plan choice in prepared statement - Mailing list pgsql-performance

From Robert Haas
Subject Re: Poor plan choice in prepared statement
Date
Msg-id 603c8f070901010544p53f01ae0x4920c6edf4c57a2c@mail.gmail.com
Whole thread Raw
In response to Re: Poor plan choice in prepared statement  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-performance
On Wed, Dec 31, 2008 at 11:01 AM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
>> The point of a prepared statement IMHO is to do the planning only once.
>> There's necessarily a tradeoff between that and having a plan that's
>> perfectly adapted to specific parameter values.
>
> I think it has been shown enough times that the performance drop caused
> by a worse plan can be orders of magnitudes worse than what's gained by
> producing the plan only once.  It does not seem a bad idea to provide a
> way to carry out only the parse phase, and postpone planning until the
> parameters have been received.

+1.

...Robert

pgsql-performance by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Poor plan choice in prepared statement
Next
From: "Guillaume Smet"
Date:
Subject: Re: Poor plan choice in prepared statement