mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Adjust a few more references to "postmaster"

Browse Source 
Reported-by: Karl O. Pinc <kop@karlpinc.com>
Discussion: https://www.postgresql.org/message-id/flat/ece84b69-8f94-8b88-925f-64207cb3a2f0@enterprisedb.com
This commit is contained in:
Peter Eisentraut 2023-01-27 08:42:08 +01:00
parent 456fa635a9
commit 17e72ec45d
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/runtime.sgml
View File

@ -1306,12 +1306,12 @@ default:\
Another kernel limit that may be of concern when supporting large Another kernel limit that may be of concern when supporting large
numbers of client connections is the maximum socket connection queue numbers of client connections is the maximum socket connection queue
length. If more than that many connection requests arrive within a very length. If more than that many connection requests arrive within a very
short period, some may get rejected before the postmaster can service short period, some may get rejected before the <productname>PostgreSQL</productname> server can service
the requests, with those clients receiving unhelpful connection failure the requests, with those clients receiving unhelpful connection failure
errors such as <quote>Resource temporarily unavailable</quote> or errors such as <quote>Resource temporarily unavailable</quote> or
<quote>Connection refused</quote>. The default queue length limit is 128 <quote>Connection refused</quote>. The default queue length limit is 128
on many platforms. To raise it, adjust the appropriate kernel parameter on many platforms. To raise it, adjust the appropriate kernel parameter
via <application>sysctl</application>, then restart the postmaster. via <application>sysctl</application>, then restart the <productname>PostgreSQL</productname> server.
The parameter is variously named <varname>net.core.somaxconn</varname> The parameter is variously named <varname>net.core.somaxconn</varname>
on Linux, <varname>kern.ipc.soacceptqueue</varname> on newer FreeBSD, on Linux, <varname>kern.ipc.soacceptqueue</varname> on newer FreeBSD,
and <varname>kern.ipc.somaxconn</varname> on macOS and other BSD and <varname>kern.ipc.somaxconn</varname> on macOS and other BSD
@ -1409,11 +1409,12 @@ sysctl -w vm.overcommit_memory=2
<programlisting> <programlisting>
echo -1000 > /proc/self/oom_score_adj echo -1000 > /proc/self/oom_score_adj
</programlisting> </programlisting>
in the postmaster's startup script just before invoking the postmaster. in the <productname>PostgreSQL</productname> startup script just before
invoking <filename>postgres</filename>.
Note that this action must be done as root, or it will have no effect; Note that this action must be done as root, or it will have no effect;
so a root-owned startup script is the easiest place to do it. If you so a root-owned startup script is the easiest place to do it. If you
do this, you should also set these environment variables in the startup do this, you should also set these environment variables in the startup
script before invoking the postmaster: script before invoking <filename>postgres</filename>:
<programlisting> <programlisting>
export PG_OOM_ADJUST_FILE=/proc/self/oom_score_adj export PG_OOM_ADJUST_FILE=/proc/self/oom_score_adj
export PG_OOM_ADJUST_VALUE=0 export PG_OOM_ADJUST_VALUE=0