Date: Thu, 12 May 2022 11:23:49 +0200
From: Christoph Berg <myon@debian.org>
To: Tomas Pospisek <tpo2@sourcepole.ch>
Cc: pgsql-pkg-debian@lists.postgresql.org
Subject: Re: Breakage: pgbouncer has changed the user under which it runs
 between 1.16.1 and 1.17.0
Message-ID: <YnzSJXNlv8mom5LO@msg.df7cb.de>
References: <c2d6beff-ab80-ad76-930f-05e4ddd9578c@sourcepole.ch>
 <YnvJcRmgVTTQCtFZ@msg.df7cb.de>
 <d8ac51a2-6684-0966-a898-aeb4e27038d6@sourcepole.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d8ac51a2-6684-0966-a898-aeb4e27038d6@sourcepole.ch>
Archived-At: 
 <https://www.postgresql.org/message-id/YnzSJXNlv8mom5LO%40msg.df7cb.de>
Precedence: bulk

Re: Tomas Pospisek
> indeed my /etc/default/pgbouncer contains `RUNASUSER="pgbouncer"`. I do set
> that explicitly via ansible. However I'm not sure where that line originated
> from. I am quite sure that it's not me who came up with the idea of running
> the daemon as `pgbouncer`, but instead that came from the package (which
> package - if from Debian or from pgdg - I don't know I would have to dig
> further, but maybe I could figure it out).

Hi Tomas,

It's true that the upstream pgbouncer default is to use "pgbouncer"
instead of "postgres", but Debian's /etc/init.d/pgbouncer has had
RUNASUSER="postgres" since 2012, and /etc/default/pgbouncer has not
been changed since 2008.

> So what is happening after the introduction of the `.service` file is that
> either `/etc/default/pgbouncer` is now beeing ignored or it is being
> overriden. That breaks installations that had `RUNASUSER="pgbouncer"` set in
> `/etc/default/pgbouncer` when upgrading to 1.17.x.
> 
> Do you concur with that conclusion?

Yes, but TBH I'd rather not reintroduce the usage of /etc/default in a
.service file when everyone else is moving away from that schema.

To override the settings from the package .service file, do this:

/etc/systemd/system/pgbouncer.service.d/user.conf:
[Service]
User=pgbouncer


Christoph