From: Peter Eisentraut <peter_e@gmx.net>
Date: Wed, 30 Nov 2016 17:00:00 +0000 (-0500)
Subject: doc: Fix typo
X-Git-Tag: REL_10_BETA1~1345
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=2f0c7ff48b68b6fb6dc373ffcebd99343a9f6451;p=postgresql.git

doc: Fix typo

From: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>
---

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