From: Tom Lane <tgl@sss.pgh.pa.us>
To: Achilleas Mantzios - cloud <a.mantzios@cloud.gatewaynet.com>
cc: pgsql-admin@lists.postgresql.org, nc@gatewaynet.com,
        Achilleas Mantzios <itdev@gatewaynet.com>
Subject: Re: application_name backend (not) reporting back to the client :
 pgbouncer, PgSQL 16.1, pgbouncer 1.21.0
In-reply-to: <e33e0231-77d7-4dd7-4b7c-97af1d0e091b@cloud.gatewaynet.com>
References: <e33e0231-77d7-4dd7-4b7c-97af1d0e091b@cloud.gatewaynet.com>
Comments: In-reply-to Achilleas Mantzios - cloud
 <a.mantzios@cloud.gatewaynet.com>
	message dated "Fri, 08 Dec 2023 12:21:30 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1436713.1702046865.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Fri, 08 Dec 2023 09:47:45 -0500
Message-ID: <1436714.1702046865@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1436714.1702046865%40sss.pgh.pa.us>
Precedence: bulk

Achilleas Mantzios - cloud <a.mantzios@cloud.gatewaynet.com> writes:
> For the past few days now we were investigating a strange issue that 
> affected our new test environment  : PostgreSQL 16.1 with pgbouncer 
> 1.21.0 . We tested with previous versions of pgbouncer against PgSQL 
> 16.1 and 10.23 and the conclusion was the problem existed only against 
> pgsql 16 no matter the pgbouncer version. Also the problem existed only 
> with pool_mode = transaction .

Surely this is a pgbouncer issue that you need to discuss with the
pgbouncer authors.  PG does not keep multiple values of application_name
per session, so you must not be connecting to the session you think
you are.

			regards, tom lane