Re: PSA: Systemd will kill PostgreSQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PSA: Systemd will kill PostgreSQL
Date: 2016-08-16 14:42:02
Message-ID: 716.1471358522@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 8/16/16 8:53 AM, Greg Stark wrote:
>> That's a system level change though. How would a normal user manage this?

> Arguably, if you are a normal user, you probably shouldn't be using
> systemd to start system services under your own account.

I'm not totally sure, but I think that the complaints were not about
systemd-driven services. (In such a case, it's almost certainly possible
to fix it by adjusting your systemd unit definition file, anyway.)
Rather, the problem arises when J. Ordinary User does

nohup postmaster &

and then logs out. That's certainly not much of a recipe for production
services but people have been known to do it for testing --- in fact,
that's pretty much what I do every day with test postmasters. I suppose
whenever I migrate to a recent-systemd-based distro I'm going to have to
turn off this miserable excuse for a feature. I sure hope there's a way
to do so.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2016-08-16 14:46:23 Re: PSA: Systemd will kill PostgreSQL
Previous Message Peter Eisentraut 2016-08-16 14:33:37 Re: PSA: Systemd will kill PostgreSQL