Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
От | Tom Lane |
---|---|
Тема | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |
Дата | |
Msg-id | 26663.1399471627@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: proposal: Set effective_cache_size to greater of .conf
value, shared_buffers
Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |
Список | pgsql-hackers |
Simon Riggs <simon@2ndQuadrant.com> writes: > I think I'm arguing myself towards using a BufferAccessStrategy of > BAS_BULKREAD for large IndexScans, BitMapIndexScans and > BitMapHeapScans. As soon as you've got some hard evidence to present in favor of such changes, we can discuss it. I've got other things to do besides hypothesize. In the meantime, it seems like there is an emerging consensus that nobody much likes the existing auto-tuning behavior for effective_cache_size, and that we should revert that in favor of just increasing the fixed default value significantly. I see no problem with a value of say 4GB; that's very unlikely to be worse than the pre-9.4 default (128MB) on any modern machine. Votes for or against? regards, tom lane
В списке pgsql-hackers по дате отправления: