From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 1 Nov 2007 19:11:31 +0000 (+0000)
Subject: Update shared-memory-size info for 8.2 branch.
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=8d139240c079aefdf8c17b36ad521c8c3d6c55cd;p=users%2Fbernd%2Fpostgres.git

Update shared-memory-size info for 8.2 branch.
---

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index ac8b60a5e7..4d9c5bd31f 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -593,7 +593,7 @@ psql: could not connect to server: No such file or directory
     <xref linkend="shared-memory-parameters">.
     You can, as a temporary solution, lower some of those settings to
     avoid the failure.  As a rough approximation, you can estimate the
-    required segment size as 500 kB plus the variable amounts shown in
+    required segment size as 700 kB plus the variable amounts shown in
     the table.  (Any error message you might get will include the exact
     size of the failed allocation request.)  While it is possible to get
     <productname>PostgreSQL</> to run with <varname>SHMMAX</> as small as
@@ -1058,12 +1058,12 @@ set semsys:seminfo_semmsl=32
      <tbody>
       <row>
        <entry><xref linkend="guc-max-connections"></>
-       <entry>400 + 270 * <xref linkend="guc-max-locks-per-transaction"></entry>
+       <entry>1800 + 270 * <xref linkend="guc-max-locks-per-transaction"></entry>
       </row>
 
       <row>
        <entry><xref linkend="guc-max-prepared-transactions"></>
-       <entry>600 + 270 * <xref linkend="guc-max-locks-per-transaction"></entry>
+       <entry>700 + 270 * <xref linkend="guc-max-locks-per-transaction"></entry>
       </row>
 
       <row>