summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-03-20 12:39:40 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2022-03-20 12:39:48 -0400
commita1efc8f8c820a1e94eb26f7c93e4c6f6e9b277d6 (patch)
tree6d231aae0eb77c90f06959330c7ff7d459202f03
parentc422e8da7ec26f7f43c05b6020fd80fd24d3c8a2 (diff)
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
-rw-r--r--doc/src/sgml/runtime.sgml8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 66c9dc7ce55..b9922ff6a83 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -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>