Re: planner with index scan cost way off actual cost,

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: planner with index scan cost way off actual cost,
Дата
Msg-id 1142974647.24487.518.camel@localhost.localdomain
обсуждение исходный текст
Ответ на planner with index scan cost way off actual cost, advices to tweak cost constants?  (Guillaume Cottenceau <gc@mnc.ch>)
Список pgsql-performance
On Fri, 2006-03-17 at 11:09 +0100, Guillaume Cottenceau wrote:

> INFO:  index "idx_sent_msgs_date_theme_status" now contains 3692284 row versions in 88057 pages

> SET effective_cache_size = 10000;

SET effective_cache_size > 88057, round up to 100000

to ensure the index cost calculation knows the whole index will be
cached, which it clearly could be with 4GB RAM.

If the cost is still wrong, it is because the index order doesn't
correlate physically with the key columns. Use CLUSTER.

Best Regards, Simon Riggs


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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Migration study, step 1: bulk write performance
Следующее
От: Ron
Дата:
Сообщение: Re: Migration study, step 1: bulk write performance