sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-31 00:03:57 -04:00
Code Issues Projects Releases Wiki Activity

Update FAQ.

Browse Source
This commit is contained in:
Bruce Momjian 2000-10-05 04:57:27 +00:00
parent e2a43d866c
commit 0f972fa02c
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/FAQ
View File

@ -605,9 +605,9 @@
should be more than that for best performance. For large numbers of should be more than that for best performance. For large numbers of
backend processes, you are also likely to find that you need to backend processes, you are also likely to find that you need to
increase various Unix kernel configuration parameters. Things to check increase various Unix kernel configuration parameters. Things to check
include the maximum size of shared memory blocks, SHMMAX, the maximum include the maximum size of shared memory blocks, SHMMAX; the maximum
number of semaphores, SEMMNS and SEMMNI, the maximum number of number of semaphores, SEMMNS and SEMMNI; the maximum number of
processes, NPROC, the maximum number of processes per user, MAXUPRC, processes, NPROC; the maximum number of processes per user, MAXUPRC;
and the maximum number of open files, NFILE and NINODE. The reason and the maximum number of open files, NFILE and NINODE. The reason
that PostgreSQL has a limit on the number of allowed backend processes that PostgreSQL has a limit on the number of allowed backend processes
is so your system won't run out of resources. is so your system won't run out of resources.

8
doc/src/FAQ/FAQ.html
View File

@ -753,10 +753,10 @@ probably should be more than that for best performance. For large
numbers of backend processes, you are also likely to find that you need numbers of backend processes, you are also likely to find that you need
to increase various Unix kernel configuration parameters. Things to to increase various Unix kernel configuration parameters. Things to
check include the maximum size of shared memory blocks, check include the maximum size of shared memory blocks,
<SMALL>SHMMAX,</SMALL> the maximum number of semaphores, <SMALL>SHMMAX;</SMALL> the maximum number of semaphores,
<SMALL>SEMMNS</SMALL> and <SMALL>SEMMNI,</SMALL> the maximum number of <SMALL>SEMMNS</SMALL> and <SMALL>SEMMNI;</SMALL> the maximum number of
processes, <SMALL>NPROC,</SMALL> the maximum number of processes per processes, <SMALL>NPROC;</SMALL> the maximum number of processes per
user, <SMALL>MAXUPRC,</SMALL> and the maximum number of open files, user, <SMALL>MAXUPRC;</SMALL> and the maximum number of open files,
<SMALL>NFILE</SMALL> and <SMALL>NINODE.</SMALL> The reason that PostgreSQL <SMALL>NFILE</SMALL> and <SMALL>NINODE.</SMALL> The reason that PostgreSQL
has a limit on the number of allowed backend processes is so has a limit on the number of allowed backend processes is so
your system won't run out of resources.<P> your system won't run out of resources.<P>