Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
14f5c845
Commit
14f5c845
authored
Feb 01, 2005
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update connections FAQ item.
parent
0c86f0e1
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
11 additions
and
40 deletions
+11
-40
doc/FAQ
doc/FAQ
+5
-18
doc/src/FAQ/FAQ.html
doc/src/FAQ/FAQ.html
+6
-22
No files found.
doc/FAQ
View file @
14f5c845
Frequently Asked Questions (FAQ) for PostgreSQL
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Mon Jan 31 1
7:58:50
EST 2005
Last updated: Mon Jan 31 1
9:18:44
EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
...
@@ -425,23 +425,10 @@
...
@@ -425,23 +425,10 @@
3.5) Why do I get "Sorry, too many clients" when trying to connect?
3.5) Why do I get "Sorry, too many clients" when trying to connect?
You need to increase postmaster's limit on how many concurrent backend
You have reached the default limit is 100 database sessions. You need
processes it can start.
to increase the postmaster's limit on how many concurrent backend
processes it can start by changing the max_connections value in
The default limit is 32 processes. You can increase it by restarting
postgresql.conf and restarting the postmaster.
postmaster with a suitable -N value or modifying postgresql.conf.
Note that if you make -N larger than 32, you must also increase -B
beyond its default of 64; -B must be at least twice -N, 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, 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.
3.6) What is in the pgsql_tmp directory?
3.6) What is in the pgsql_tmp directory?
...
...
doc/src/FAQ/FAQ.html
View file @
14f5c845
...
@@ -10,7 +10,7 @@
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated: Mon Jan 31 1
7:58:50
EST 2005
</P>
<P>
Last updated: Mon Jan 31 1
9:18:44
EST 2005
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:pgman@candle.pha.pa.us"
>
pgman@candle.pha.pa.us
</A>
)
"mailto:pgman@candle.pha.pa.us"
>
pgman@candle.pha.pa.us
</A>
)
...
@@ -568,27 +568,11 @@
...
@@ -568,27 +568,11 @@
<H4><A
name=
"3.5"
>
3.5
</A>
) Why do I get
<I>
"Sorry, too many
<H4><A
name=
"3.5"
>
3.5
</A>
) Why do I get
<I>
"Sorry, too many
clients"
</I>
when trying to connect?
</H4>
clients"
</I>
when trying to connect?
</H4>
<P>
You need to increase
<I>
postmaster
</I>
's limit on how many
You have reached the default limit is 100 database sessions. You
concurrent backend processes it can start.
</P>
need to increase the
<I>
postmaster
</I>
's limit on how many
concurrent backend processes it can start by changing the
<P>
The default limit is 32 processes. You can increase it by
<I>
max_connections
</I>
value in
<I>
postgresql.conf
</I>
and
restarting
<I>
postmaster
</I>
with a suitable
<I>
-N
</I>
value or
restarting the
<I>
postmaster
</I>
.
</P>
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>
<H4><A
name=
"3.6"
>
3.6
</A>
) What is in the
<I>
pgsql_tmp
</I>
directory?
</H4>
<H4><A
name=
"3.6"
>
3.6
</A>
) What is in the
<I>
pgsql_tmp
</I>
directory?
</H4>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment