Re: prepared query performs much worse than regular query

Поиск
Список
Период
Сортировка
От Matthew Wakeling
Тема Re: prepared query performs much worse than regular query
Дата
Msg-id alpine.DEB.2.00.1005212324070.2887@aragorn.flymine.org
обсуждение исходный текст
Ответ на prepared query performs much worse than regular query  (Richard Yen <dba@richyen.com>)
Ответы Re: prepared query performs much worse than regular query  (Scott Carey <scott@richrelevance.com>)
Список pgsql-performance
On Fri, 21 May 2010, Richard Yen wrote:
> Any ideas why the query planner chooses a different query plan when using prepared statements?

This is a FAQ. Preparing a statement makes Postgres create a plan, without
knowing the values that you will plug in, so it will not be as optimal as
if the values were available. The whole idea is to avoid the planning cost
each time the query is executed, but if your data is unusual it can
result in worse plans.

Matthew

--
 Existence is a convenient concept to designate all of the files that an
 executable program can potentially process.   -- Fortran77 standard

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

Предыдущее
От: Rosser Schwarz
Дата:
Сообщение: Re: prepared query performs much worse than regular query
Следующее
От: David Jarvis
Дата:
Сообщение: Re: Optimize date query for large child tables: GiST or GIN?