Re: FTS performance issue - planner problem identified (but only partially resolved)

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: FTS performance issue - planner problem identified (but only partially resolved)
Дата
Msg-id 1375129736.38828.YahooMailNeo@web162901.mail.bf1.yahoo.com
обсуждение исходный текст
Ответ на FTS performance issue - planner problem identified (but only partially resolved)  (Stefan Keller <sfkeller@gmail.com>)
Ответы Re: FTS performance issue - planner problem identified (but only partially resolved)  (Stefan Keller <sfkeller@gmail.com>)
Список pgsql-performance
Дерево обсуждения 
Stefan Keller <sfkeller@gmail.com> wrote:

> Finally, setting random_page_cost to 1 helps also - but I don't
> like this setting neither.

Well, you should learn to like whichever settings best model your
actual costs given your level of caching and your workload.  ;-)
FWIW, I have found page costs less volatile and easier to tune
with cpu_tuple_cost increased.  I just always start by bumping
that to 0.03.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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

Предыдущее
От: Jeff Janes
Дата:
Сообщение: Re: How is memory allocated/used by Postgresql Database connections
Следующее
От: Stefan Keller
Дата:
Сообщение: Re: FTS performance issue - planner problem identified (but only partially resolved)