diff options
| author | Bruce Momjian <bruce@momjian.us> | 2000-10-05 04:57:27 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2000-10-05 04:57:27 +0000 |
| commit | 0f972fa02c0b42d498399a575dba7998837858ab (patch) | |
| tree | d7eb8dcdc53f67fb8e579d98103309664d3444bb /doc/src/FAQ/FAQ.html | |
| parent | e2a43d866c41bf201c9d7caaf0237576aec3a3d4 (diff) | |
| download | postgresql-0f972fa02c0b42d498399a575dba7998837858ab.tar.gz postgresql-0f972fa02c0b42d498399a575dba7998837858ab.zip | |
Update FAQ.
Diffstat (limited to 'doc/src/FAQ/FAQ.html')
| -rw-r--r-- | doc/src/FAQ/FAQ.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index bae3c6490dc..e51b4fa2703 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -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 to increase various Unix kernel configuration parameters. Things to check include the maximum size of shared memory blocks, -<SMALL>SHMMAX,</SMALL> the maximum number of semaphores, -<SMALL>SEMMNS</SMALL> and <SMALL>SEMMNI,</SMALL> the maximum number of -processes, <SMALL>NPROC,</SMALL> the maximum number of processes per -user, <SMALL>MAXUPRC,</SMALL> and the maximum number of open files, +<SMALL>SHMMAX;</SMALL> the maximum number of semaphores, +<SMALL>SEMMNS</SMALL> and <SMALL>SEMMNI;</SMALL> the maximum number of +processes, <SMALL>NPROC;</SMALL> the maximum number of processes per +user, <SMALL>MAXUPRC;</SMALL> and the maximum number of open files, <SMALL>NFILE</SMALL> and <SMALL>NINODE.</SMALL> The reason that PostgreSQL has a limit on the number of allowed backend processes is so your system won't run out of resources.<P> |