Re: Poor plan choice in prepared statement

Поиск
Список
Период
Сортировка
От david@lang.hm
Тема Re: Poor plan choice in prepared statement
Дата
Msg-id alpine.DEB.1.10.0901011239140.15026@asgard.lang.hm
обсуждение исходный текст
Ответ на Re: Poor plan choice in prepared statement  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Ответы Re: Poor plan choice in prepared statement
Список pgsql-performance
On Thu, 1 Jan 2009, Guillaume Smet wrote:

> On Thu, Jan 1, 2009 at 9:24 PM,  <david@lang.hm> wrote:
>> forgive my ignorance here, but if it's unnamed how can you reference it
>> later to take advantage of the parsing?
>
> You can't. That's what unnamed prepared statements are for.
>
> It's not obvious to me that the parsing phase is worth any "caching".
> From my experience, the planning phase takes far much time on complex
> queries.

the poster who started this thread had a query where the parsing phase
took significantly longer than the planning stage.

David Lang

В списке pgsql-performance по дате отправления:

Предыдущее
От: "Guillaume Smet"
Дата:
Сообщение: Re: Poor plan choice in prepared statement
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Poor plan choice in prepared statement