Re: 4s query want to run faster

Поиск
Список
Период
Сортировка
Искать
От
Mark Kirkwood
Тема
Re: 4s query want to run faster
Дата
Msg-id
47BE023A.6000905@paradise.net.nz
Ответ на
Список
Дерево обсуждения
4s query want to run faster "Adonias Malosso" <malosso@gmail.com>
Re: 4s query want to run faster "Claus Guttesen" <kometen@gmail.com>
Re: 4s query want to run faster "Adonias Malosso" <malosso@gmail.com>
Re: 4s query want to run faster "Claus Guttesen" <kometen@gmail.com>
Re: 4s query want to run faster "Adonias Malosso" <malosso@gmail.com>
Re: 4s query want to run faster Mark Kirkwood <markir@paradise.net.nz>
Re: 4s query want to run faster "Scott Marlowe" <scott.marlowe@gmail.com>
Re: 4s query want to run faster Mark Kirkwood <markir@paradise.net.nz>
Re: 4s query want to run faster Dave Cramer <pg@fastcrypt.com>
Re: 4s query want to run faster "Scott Marlowe" <scott.marlowe@gmail.com>
Re: 4s query want to run faster "Adonias Malosso" <malosso@gmail.com>
Re: 4s query want to run faster "Scott Marlowe" <scott.marlowe@gmail.com>
The other parameter you might want to look at is effective_cache_size - 
increasing it will encourage index use. On a machine with 16GB the 
default is probably too small (there are various recommendations about 
how to set this ISTR either Scott M or Greg Smith had a page somewhere 
that covered this quite well - guys?).

Obviously, decreasing random_page_cost fixed this query for you, but if 
find yourself needing to tweak it again for other queries, then look at 
changing effective_cache_size.

Cheers

Mark


Adonias Malosso wrote:
> Set random_page_cost = 2 solved the problem. thanks
>

В списке pgsql-performance по дате отправления
От: Scott Marlowe
Дата:
От: Scott Marlowe
Дата:
FAQ