aboutsummaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2000-10-05 04:57:27 +0000
committerBruce Momjian <bruce@momjian.us>2000-10-05 04:57:27 +0000
commit0f972fa02c0b42d498399a575dba7998837858ab (patch)
treed7eb8dcdc53f67fb8e579d98103309664d3444bb /doc/FAQ
parente2a43d866c41bf201c9d7caaf0237576aec3a3d4 (diff)
downloadpostgresql-0f972fa02c0b42d498399a575dba7998837858ab.tar.gz
postgresql-0f972fa02c0b42d498399a575dba7998837858ab.zip
Update FAQ.
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 6bc484440f5..8d00befa3e7 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -605,9 +605,9 @@
should be more than that for best performance. For large numbers of
backend processes, you are also likely to find that you need to
increase various Unix kernel configuration parameters. Things to check
- include the maximum size of shared memory blocks, SHMMAX, the maximum
- number of semaphores, SEMMNS and SEMMNI, the maximum number of
- processes, NPROC, the maximum number of processes per user, MAXUPRC,
+ include the maximum size of shared memory blocks, SHMMAX; the maximum
+ number of semaphores, SEMMNS and SEMMNI; the maximum number of
+ processes, NPROC; the maximum number of processes per user, MAXUPRC;
and the maximum number of open files, NFILE and NINODE. The reason
that PostgreSQL has a limit on the number of allowed backend processes
is so your system won't run out of resources.