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
Date: Fri, 08 Dec 2023 09:47:45 -0500
Message-ID: <1436714.1702046865@sss.pgh.pa.us> (raw)
In-Reply-To: <e33e0231-77d7-4dd7-4b7c-97af1d0e091b@cloud.gatewaynet.com>
References: <e33e0231-77d7-4dd7-4b7c-97af1d0e091b@cloud.gatewaynet.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, a.mantzios@cloud.gatewaynet.com, 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: <1436714.1702046865@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox