postgres.git / summary / log / commit / refs

commit    88418aacc9ff94a0a84b1d26ea6d64d0d5d1ecda
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Sun Mar 20 16:39:40 2022 +0000
First released in: 15.0, 10.21, 11.16, 12.11, 13.7, 14.3

    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 b2b5a092925..833268e812d 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -443,7 +443,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
@@ -455,11 +455,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>
 


[parent: 4d2322925187]