Re: Large tables, ORDER BY and sequence/index scans

Поиск
Список
Период
Сортировка
От John R Pierce
Тема Re: Large tables, ORDER BY and sequence/index scans
Дата
Msg-id 4B4373E6.9080208@hogranch.com
обсуждение исходный текст
Ответ на Re: Large tables, ORDER BY and sequence/index scans  (Milan Zamazal <pdm@brailcom.org>)
Ответы Re: Large tables, ORDER BY and sequence/index scans  (Milan Zamazal <pdm@brailcom.org>)
Список pgsql-general
Milan Zamazal wrote:
>     PS> and value efective_cache_size ???
>
> effective_cache_size = 128MB
>

thats rather small unless your systme is very memory constrained.
assuming postgres is the primary disk IO consumer on this ysstem, take a
look at the 'cached' value on TOP or whatever after its been running,
thats a good first order estimate of effective_cache_size.... this is
often half or more of your physical memory.



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

Предыдущее
От: frank joerdens
Дата:
Сообщение: reason for default PGSTAT_ACTIVITY_SIZE
Следующее
От: Merlin Moncure
Дата:
Сообщение: pl/perl not rethrowing pl/pgsql exceptions