postgres.git / summary / log / commit / refs

commit    2f0c7ff48b68b6fb6dc373ffcebd99343a9f6451
Author:   Peter Eisentraut <peter_e@gmx.net>
Date:     Wed Nov 30 17:00:00 2016 +0000

    doc: Fix typo
    
    From: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>


 doc/src/sgml/config.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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


[parent: 1de9cc0dcca6]