public inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedFrom: Peter Eisentraut <peter@eisentraut.org>
To: Andrew Jackson <andrewjackson947@gmail.com>
To: pgsql-docs@postgresql.org
Subject: Re: Add Restart=on-failure To Example Systemd File
Date: Tue, 3 Mar 2026 13:22:13 +0100
Message-ID: <61063be9-abbc-4253-ac8e-2762c9997a24@eisentraut.org> (raw)
In-Reply-To: <CAKK5BkFfMpAQnv8CLs=i=rZwurtCV_gmfRb0uZi-V+d6wcryqg@mail.gmail.com>
References: <CAKK5BkFfMpAQnv8CLs=i=rZwurtCV_gmfRb0uZi-V+d6wcryqg@mail.gmail.com>
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.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: peter@eisentraut.org, andrewjackson947@gmail.com
Subject: Re: Add Restart=on-failure To Example Systemd File
In-Reply-To: <61063be9-abbc-4253-ac8e-2762c9997a24@eisentraut.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox