Date: Wed, 11 May 2022 16:34:25 +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: <YnvJcRmgVTTQCtFZ@msg.df7cb.de>
References: <c2d6beff-ab80-ad76-930f-05e4ddd9578c@sourcepole.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c2d6beff-ab80-ad76-930f-05e4ddd9578c@sourcepole.ch>
Archived-At: 
 <https://www.postgresql.org/message-id/YnvJcRmgVTTQCtFZ%40msg.df7cb.de>
Precedence: bulk

Re: Tomas Pospisek
> Due to the change of user under which pgbouncer runs (before: user
> pgbouncer, new: user postgres), an upgrade from 1.16.1 to 1.17.0 will break
> systems.

Hi Tomas,

the Debian pgbouncer package has always been using the postgres user:

$ grep USER debian/init
RUNASUSER="postgres"
    $SSD --start --chuid $RUNASUSER --oknodo -- $OPTS 2> /dev/null
        su -c "$DAEMON -R $OPTS 2> /dev/null" - ${RUNASUSER%:*}

Maybe you were editing the init.d or defaults file before?

>     Upgrade: pgbouncer:amd64 (1.16.1-1.pgdg20.04+1,
>              1.17.0-3.pgdg20.04+1)

The effective change between these versions is that we are now
shipping a .service file.

Christoph