Commit88418aa

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 parent4d23229 commit88418aaCopy full SHA for 88418aa

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -443,7 +443,7 @@ ExecStart=/usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data`
`443`	`443`	`ExecReload=/bin/kill -HUP $MAINPID`
`444`	`444`	`KillMode=mixed`
`445`	`445`	`KillSignal=SIGINT`
`446`		`-TimeoutSec=0`
	`446`	`+TimeoutSec=infinity`
`447`	`447`
`448`	`448`	`[Install]`
`449`	`449`	`WantedBy=multi-user.target`
`@@ -455,11 +455,11 @@ WantedBy=multi-user.target`
`455`	`455`	`<para>`
`456`	`456`	`Consider carefully the timeout`
`457`	`457`	`setting. <application>systemd</application> has a default timeout of 90`
`458`		`- seconds as of this writing and will kill a process that does notnotify`
	`458`	`+ seconds as of this writing and will kill a process that does notreport`
`459`	`459`	`readiness within that time. But a <productname>PostgreSQL</productname>`
`460`	`460`	`server that might have to perform crash recovery at startup could take`
`461`		`- much longer to become ready. The suggested value of 0 disables the`
`462`		`- timeout logic.`
	`461`	`+ much longer to become ready. The suggested value`
	`462`	`+of <literal>infinity</literal> disables thetimeout logic.`
`463`	`463`	`</para>`
`464`	`464`	`</listitem>`
`465`	`465`

Comments

(0)