summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane2004-02-23 20:46:16 +0000
committerTom Lane2004-02-23 20:46:16 +0000
commit95a6dbf12b2aa7261cd6f13f41cc8de8a693ee75 (patch)
tree03985fbffc9a34f8e9ca3a58cacbbb7f49aed89f /doc/src
parentfd7d98a271e65bc982e9af0f76b765ef50baa247 (diff)
Do a direct probe during postmaster startup to determine the maximum
number of openable files and the number already opened. This eliminates depending on sysconf(_SC_OPEN_MAX), and allows much saner behavior on platforms where open-file slots are used up by semaphores.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/runtime.sgml23
1 files changed, 9 insertions, 14 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 8232ddc664c..64b4d11d18b 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.215.2.6 2003/11/24 14:50:02 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.215.2.7 2004/02/23 20:46:16 tgl Exp $
-->
<Chapter Id="runtime">
@@ -928,19 +928,14 @@ SET ENABLE_SEQSCAN TO OFF;
<listitem>
<para>
Sets the maximum number of simultaneously open files allowed to each
- server subprocess. The default is 1000. The limit actually used
- by the code is the smaller of this setting and the result of
- <literal>sysconf(_SC_OPEN_MAX)</literal>. Therefore, on systems
- where <function>sysconf</> returns a reasonable limit, you don't
- need to worry about this setting. But on some platforms
- (notably, most BSD systems), <function>sysconf</> returns a
- value that is much larger than the system can really support
- when a large number of processes all try to open that many
- files. If you find yourself seeing <quote>Too many open files</>
- failures, try reducing this setting. This option can only be set
- at server start or in the <filename>postgresql.conf</filename>
- configuration file; if changed in the configuration file, it
- only affects subsequently-started server subprocesses.
+ server subprocess. The default is 1000. If the kernel is enforcing
+ a safe per-process limit, you don't need to worry about this setting.
+ But on some platforms (notably, most BSD systems), the kernel will
+ allow individual processes to open many more files than the system
+ can really support when a large number of processes all try to open
+ that many files. If you find yourself seeing <quote>Too many open
+ files</> failures, try reducing this setting.
+ This option can only be set at server start.
</para>
</listitem>
</varlistentry>