From 0de9b999d14f7c529c0a47b24198442b404db084 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 20 Mar 2022 12:39:40 -0400 Subject: [PATCH] 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 --- doc/src/sgml/runtime.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 5a620d0d32c..f56f9cfbea3 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -395,7 +395,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 @@ -407,11 +407,11 @@ WantedBy=multi-user.target Consider carefully the timeout setting. systemd 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 PostgreSQL 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 infinity disables the timeout logic. -- 2.39.5