Re: Remove the comment on the countereffectiveness of large shared_buffers on Windows
От | amul sul |
---|---|
Тема | Re: Remove the comment on the countereffectiveness of large shared_buffers on Windows |
Дата | |
Msg-id | CAAJ_b96G4d4FQjRLKycoiV-QiXg1hUqf0F0phYYZ+U_YS18YXA@mail.gmail.com обсуждение исходный текст |
Ответ на | Remove the comment on the countereffectiveness of large shared_buffers on Windows ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>) |
Ответы |
Re: Remove the comment on the countereffectiveness of
large shared_buffers on Windows
Re: Remove the comment on the countereffectiveness of large shared_buffers on Windows |
Список | pgsql-hackers |
Hi Takayuki-san, IMHO, I think we could remove third paragraph completely and generalised starting of second paragraph, somewhat looks likes as follow: <para> - If you have a dedicated database server with 1GB or more of RAM, a - reasonable starting value for <varname>shared_buffers</varname> is 25% - of the memory in your system. There are some workloads where even + A reasonable starting value for <varname>shared_buffers</varname> is 25% + of the RAM in your system. There are some workloads where even large settings for <varname>shared_buffers</varname>are effective, but because <productname>PostgreSQL</productname> also relies on the operating system cache, it is unlikely that an allocation of more than I may be wrong here, would like know your and/or community's thought on this. Thanks. Regards, Amul Sul The new status of this patch is: Waiting on Author
В списке pgsql-hackers по дате отправления: