Feedback-ID: ie0a040ee:Fastmail
Message-ID: <61063be9-abbc-4253-ac8e-2762c9997a24@eisentraut.org>
Date: Tue, 3 Mar 2026 13:22:13 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Add Restart=on-failure To Example Systemd File
To: Andrew Jackson <andrewjackson947@gmail.com>, pgsql-docs@postgresql.org
References: 
 <CAKK5BkFfMpAQnv8CLs=i=rZwurtCV_gmfRb0uZi-V+d6wcryqg@mail.gmail.com>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: 
 <CAKK5BkFfMpAQnv8CLs=i=rZwurtCV_gmfRb0uZi-V+d6wcryqg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/61063be9-abbc-4253-ac8e-2762c9997a24%40eisentraut.org>
Precedence: bulk

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.