| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Andrew Jackson <andrewjackson947(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Add Restart=on-failure To Example Systemd File |
| Date: | 2026-03-03 12:22:13 |
| Message-ID: | 61063be9-abbc-4253-ac8e-2762c9997a24@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 27.11.25 19:55, Andrew Jackson wrote:
> Currently the systemd file in the documentation does not specify a
> restart policy. By default systemd will not attempt to restart a
> service that has failed (killed by OOM-killer for example) [0]. The
> systemd docs recommends "Setting this to on-failure is the recommended
> choice for long-running services, in order to increase reliability by
> attempting automatic recovery from errors." I think that Postgres is
> probably a good example of a "long-running service". Pgbouncer for
> example also uses "Restart=on-failure" [1].
Committed.
I think your argument from the commit message that most users copy their
systemd unit files from the docs is not quite correct. Most users use
what is in packages. So perhaps you want to check the usual packagings
and see if they are also using that setting.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Jackson | 2026-03-03 14:56:46 | Re: Add Restart=on-failure To Example Systemd File |
| Previous Message | Laurenz Albe | 2026-02-28 20:12:06 | Re: Documentation incorrect pg_partition_root function description. |