mirror of
https://github.com/postgres/postgres.git
synced 2025-04-25 21:42:33 +03:00
Doc: fix our example systemd script.
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:
parent
c422e8da7e
commit
a1efc8f8c8
@ -488,7 +488,7 @@ ExecStart=/usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data
|
||||
ExecReload=/bin/kill -HUP $MAINPID
|
||||
KillMode=mixed
|
||||
KillSignal=SIGINT
|
||||
TimeoutSec=0
|
||||
TimeoutSec=infinity
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
@ -500,11 +500,11 @@ WantedBy=multi-user.target
|
||||
<para>
|
||||
Consider carefully the timeout
|
||||
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>
|
||||
server that might have to perform crash recovery at startup could take
|
||||
much longer to become ready. The suggested value of 0 disables the
|
||||
timeout logic.
|
||||
much longer to become ready. The suggested value
|
||||
of <literal>infinity</literal> disables the timeout logic.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user