summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2016-11-30 12:00:00 -0500
committerPeter Eisentraut <peter_e@gmx.net>2016-11-30 09:38:44 -0500
commit81c52728f82be5303ea16508255e948017f4cd87 (patch)
tree217c6e8d2918d5839d146c5dba400e7d7c6d265e
parent2f0c7ff48b68b6fb6dc373ffcebd99343a9f6451 (diff)
doc: Remove claim about large shared_buffers on Windows
Testing has shown that it is no longer correct. From: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com> Reviewed-by: amul sul <sulamul@gmail.com> Discussion: http://www.postgresql.org/message-id/flat/0A3221C70F24FB45833433255569204D1F5EE995@G01JPEXMBYT05/
-rw-r--r--doc/src/sgml/config.sgml5
1 files changed, 0 insertions, 5 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index bcfe2fded29..b1c5289fccc 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1316,11 +1316,6 @@ include_dir 'conf.d'
<para>
On systems with less than 1GB of RAM, a smaller percentage of RAM is
appropriate, so as to leave adequate space for the operating system.
- Also, on Windows, large values for <varname>shared_buffers</varname>
- aren't as effective. You may find better results keeping the setting
- relatively low and using the operating system cache more instead. The
- useful range for <varname>shared_buffers</varname> on Windows systems
- is generally from 64MB to 512MB.
</para>
</listitem>