Commit3f513ac

committed

Doc: fix our example systemd script.

The example used "TimeoutSec=0", but systemd's documented way to getthe desired effect is "TimeoutSec=infinity".Discussion:https://postgr.es/m/164770078557.670.5467111518383664377@wrigleys.postgresql.org

1 parent3a671e1 commit3f513acCopy full SHA for 3f513ac

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -488,7 +488,7 @@ ExecStart=/usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data`
`488`	`488`	`ExecReload=/bin/kill -HUP $MAINPID`
`489`	`489`	`KillMode=mixed`
`490`	`490`	`KillSignal=SIGINT`
`491`		`-TimeoutSec=0`
	`491`	`+TimeoutSec=infinity`
`492`	`492`
`493`	`493`	`[Install]`
`494`	`494`	`WantedBy=multi-user.target`
`@@ -500,11 +500,11 @@ WantedBy=multi-user.target`
`500`	`500`	`<para>`
`501`	`501`	`Consider carefully the timeout`
`502`	`502`	`setting. <application>systemd</application> has a default timeout of 90`
`503`		`- seconds as of this writing and will kill a process that does notnotify`
	`503`	`+ seconds as of this writing and will kill a process that does notreport`
`504`	`504`	`readiness within that time. But a <productname>PostgreSQL</productname>`
`505`	`505`	`server that might have to perform crash recovery at startup could take`
`506`		`- much longer to become ready. The suggested value of 0 disables the`
`507`		`- timeout logic.`
	`506`	`+ much longer to become ready. The suggested value`
	`507`	`+of <literal>infinity</literal> disables thetimeout logic.`
`508`	`508`	`</para>`
`509`	`509`	`</listitem>`
`510`	`510`

Comments

(0)