From: Tom Lane Date: Tue, 30 Aug 2005 15:48:28 +0000 (+0000) Subject: Remove a couple of obsolete statements about how many buffers you can X-Git-Tag: REL8_1_0BETA2~70 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=571be6f381713aa8a70f0cb381706a09acb18f84;p=postgresql Remove a couple of obsolete statements about how many buffers you can fit into a 512K shared memory segment. --- diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 37d4c44254..5af562a663 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -362,8 +362,8 @@ DETAIL: Failed system call was shmget(key=5440001, size=4011376640, 03600). is trying to create (4011376640 bytes in this example). Or it could mean that you do not have System-V-style shared memory support configured into your kernel at all. As a temporary workaround, you - can try starting the server with a smaller-than-normal number - of buffers ( switch). You will eventually want + can try starting the server with a smaller-than-normal number of + buffers (). You will eventually want to reconfigure your kernel to increase the allowed shared memory size. You may also see this message when trying to start multiple servers on the same machine, if their total space requested @@ -382,7 +382,7 @@ DETAIL: Failed system call was semget(5440126, 17, 03600). PostgreSQL wants to create. As above, you may be able to work around the problem by starting the server with a reduced number of allowed connections - ( switch), but you'll eventually want to + (), but you'll eventually want to increase the kernel limit. @@ -5116,9 +5116,8 @@ sysctl -w kern.sysv.shmall In the default configuration, only 512 kB of shared memory per - segment is allowed, which is about enough for