Re: Poor plan choice in prepared statement

Поиск
Список
Период
Сортировка
От Guillaume Smet
Тема Re: Poor plan choice in prepared statement
Дата
Msg-id 1d4e0c10901011022v4a1d5eeaidc2692a7729e79df@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Poor plan choice in prepared statement  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: Poor plan choice in prepared statement  (david@lang.hm)
Список 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 по дате отправления:

Предыдущее
От: "Robert Haas"
Дата:
Сообщение: Re: Poor plan choice in prepared statement
Следующее
От: david@lang.hm
Дата:
Сообщение: Re: Poor plan choice in prepared statement