database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Update connections FAQ item.

Browse Source
This commit is contained in:
Bruce Momjian
2005-02-01 00:19:15 +00:00
parent 0c86f0e174
commit 14f5c84589
2 changed files with 11 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -10,7 +10,7 @@
alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
<P>Last updated: Mon Jan 31 17:58:50 EST 2005</P>
<P>Last updated: Mon Jan 31 19:18:44 EST 2005</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@ -568,27 +568,11 @@
<H4><A name="3.5">3.5</A>) Why do I get <I>"Sorry, too many
clients"</I> when trying to connect?</H4>
<P>You need to increase <I>postmaster</I>'s limit on how many
concurrent backend processes it can start.</P>
<P>The default limit is 32 processes. You can increase it by
restarting <I>postmaster</I> with a suitable <I>-N</I> value or
modifying <I>postgresql.conf</I>.</P>
<P>Note that if you make <I>-N</I> larger than 32, you must also
increase <I>-B</I> beyond its default of 64; <I>-B</I> must be at
least twice <I>-N</I>, and 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>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>
You have reached the default limit is 100 database sessions. You
need to increase the <I>postmaster</I>'s limit on how many
concurrent backend processes it can start by changing the
<I>max_connections</I> value in <I>postgresql.conf</I> and
restarting the <I>postmaster</I>.</P>
<H4><A name="3.6">3.6</A>) What is in the <I>pgsql_tmp</I> directory?</H4>