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

From Guillaume Smet
Subject Re: Poor plan choice in prepared statement
Date
Msg-id 1d4e0c10901011022v4a1d5eeaidc2692a7729e79df@mail.gmail.com
Whole thread Raw
In response to Re: Poor plan choice in prepared statement  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Poor plan choice in prepared statement
List pgsql-performance
On Wed, Dec 31, 2008 at 5:01 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> 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.

It's already done in 8.3 for unnamed plans, isn't it?

--
Guillaume

pgsql-performance by date:

Previous
From: "Robert Haas"
Date:
Subject: Re: Poor plan choice in prepared statement
Next
From: david@lang.hm
Date:
Subject: Re: Poor plan choice in prepared statement