Re: Poor plan choice in prepared statement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 1 Jan 2009, Guillaume Smet wrote:

On Wed, Dec 31, 2008 at 5:01 PM, Alvaro Herrera
<alvherre@xxxxxxxxxxxxxxxxx> 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?

forgive my ignorance here, but if it's unnamed how can you reference it later to take advantage of the parsing?

I may just be not understanding the terms being used here.

David Lang

--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux