diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2016-11-30 12:00:00 -0500 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2016-11-30 09:23:51 -0500 |
| commit | 2f0c7ff48b68b6fb6dc373ffcebd99343a9f6451 (patch) | |
| tree | 80bb64eaa7c0c3b3f8ac909a14486f3732adf682 | |
| parent | 1de9cc0dcca649d1900720924f4ea5c430d1a51e (diff) | |
doc: Fix typo
From: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>
| -rw-r--r-- | doc/src/sgml/config.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index d8d207e5eb9..bcfe2fded29 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1302,7 +1302,7 @@ include_dir 'conf.d' 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 - large settings for <varname>shared_buffers</varname> are effective, but + larger 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 40% of RAM to <varname>shared_buffers</varname> will work better than a |