database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-03 09:13:20 +03:00
Code Activity

Doc: fix our example systemd script.

Browse Source 
The example used "TimeoutSec=0", but systemd's documented way to get
the desired effect is "TimeoutSec=infinity".

Discussion: https://postgr.es/m/164770078557.670.5467111518383664377@wrigleys.postgresql.org
This commit is contained in:
Tom Lane
2022-03-20 12:39:40 -04:00
parent 4d23229251
commit 88418aacc9
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -443,7 +443,7 @@ ExecStart=/usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data
ExecReload=/bin/kill -HUP $MAINPID ExecReload=/bin/kill -HUP $MAINPID
KillMode=mixed KillMode=mixed
KillSignal=SIGINT KillSignal=SIGINT
TimeoutSec=0 TimeoutSec=infinity
[Install] [Install]
WantedBy=multi-user.target WantedBy=multi-user.target
@@ -455,11 +455,11 @@ WantedBy=multi-user.target
<para> <para>
Consider carefully the timeout Consider carefully the timeout
setting. <application>systemd</application> has a default timeout of 90 setting. <application>systemd</application> has a default timeout of 90
seconds as of this writing and will kill a process that does not notify seconds as of this writing and will kill a process that does not report
readiness within that time. But a <productname>PostgreSQL</productname> readiness within that time. But a <productname>PostgreSQL</productname>
server that might have to perform crash recovery at startup could take server that might have to perform crash recovery at startup could take
much longer to become ready. The suggested value of 0 disables the much longer to become ready. The suggested value
timeout logic. of <literal>infinity</literal> disables the timeout logic.
</para> </para>
</listitem> </listitem>