Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit14f5c84

Browse files
committed
Update connections FAQ item.
1 parent0c86f0e commit14f5c84

File tree

2 files changed

+11
-40
lines changed

2 files changed

+11
-40
lines changed

‎doc/FAQ

Lines changed: 5 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Mon Jan 3117:58:50 EST 2005
4+
Last updated: Mon Jan 3119:18:44 EST 2005
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -425,23 +425,10 @@
425425

426426
3.5) Why do I get "Sorry, too many clients" when trying to connect?
427427

428-
You need to increase postmaster's limit on how many concurrent backend
429-
processes it can start.
430-
431-
The default limit is 32 processes. You can increase it by restarting
432-
postmaster with a suitable -N value or modifying postgresql.conf.
433-
434-
Note that if you make -N larger than 32, you must also increase -B
435-
beyond its default of 64; -B must be at least twice -N, and probably
436-
should be more than that for best performance. For large numbers of
437-
backend processes, you are also likely to find that you need to
438-
increase various Unix kernel configuration parameters. Things to check
439-
include the maximum size of shared memory blocks, SHMMAX; the maximum
440-
number of semaphores, SEMMNS and SEMMNI; the maximum number of
441-
processes, NPROC; the maximum number of processes per user, MAXUPRC;
442-
and the maximum number of open files, NFILE and NINODE. The reason
443-
that PostgreSQL has a limit on the number of allowed backend processes
444-
is so your system won't run out of resources.
428+
You have reached the default limit is 100 database sessions. You need
429+
to increase the postmaster's limit on how many concurrent backend
430+
processes it can start by changing the max_connections value in
431+
postgresql.conf and restarting the postmaster.
445432

446433
3.6) What is in the pgsql_tmp directory?
447434

‎doc/src/FAQ/FAQ.html

Lines changed: 6 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
alink="#0000ff">
1111
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1212

13-
<P>Last updated: Mon Jan 3117:58:50 EST 2005</P>
13+
<P>Last updated: Mon Jan 3119:18:44 EST 2005</P>
1414

1515
<P>Current maintainer: Bruce Momjian (<Ahref=
1616
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@@ -568,27 +568,11 @@ <H4><A name="3.4">3.4</A>) What debugging features are
568568
<H4><Aname="3.5">3.5</A>) Why do I get<I>"Sorry, too many
569569
clients"</I> when trying to connect?</H4>
570570

571-
<P>You need to increase<I>postmaster</I>'s limit on how many
572-
concurrent backend processes it can start.</P>
573-
574-
<P>The default limit is 32 processes. You can increase it by
575-
restarting<I>postmaster</I> with a suitable<I>-N</I> value or
576-
modifying<I>postgresql.conf</I>.</P>
577-
578-
<P>Note that if you make<I>-N</I> larger than 32, you must also
579-
increase<I>-B</I> beyond its default of 64;<I>-B</I> must be at
580-
least twice<I>-N</I>, and probably should be more than that for
581-
best performance. For large numbers of backend processes, you are
582-
also likely to find that you need to increase various Unix kernel
583-
configuration parameters. Things to check include the maximum size
584-
of shared memory blocks,<SMALL>SHMMAX;</SMALL> the maximum number
585-
of semaphores,<SMALL>SEMMNS</SMALL> and<SMALL>SEMMNI;</SMALL> the
586-
maximum number of processes,<SMALL>NPROC;</SMALL> the maximum
587-
number of processes per user,<SMALL>MAXUPRC;</SMALL> and the
588-
maximum number of open files,<SMALL>NFILE</SMALL> and
589-
<SMALL>NINODE</SMALL>. The reason that PostgreSQL has a limit on
590-
the number of allowed backend processes is so your system won't run
591-
out of resources.</P>
571+
You have reached the default limit is 100 database sessions. You
572+
need to increase the<I>postmaster</I>'s limit on how many
573+
concurrent backend processes it can start by changing the
574+
<I>max_connections</I> value in<I>postgresql.conf</I> and
575+
restarting the<I>postmaster</I>.</P>
592576

593577
<H4><Aname="3.6">3.6</A>) What is in the<I>pgsql_tmp</I> directory?</H4>
594578

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp