Re: application_name backend (not) reporting back to the client : pgbouncer, PgSQL 16.1, pgbouncer 1.21.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Achilleas Mantzios - cloud <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org, nc(at)gatewaynet(dot)com, Achilleas Mantzios <itdev(at)gatewaynet(dot)com>
Subject: Re: application_name backend (not) reporting back to the client : pgbouncer, PgSQL 16.1, pgbouncer 1.21.0
Date: 2023-12-08 14:47:45
Message-ID: 1436714.1702046865@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Achilleas Mantzios - cloud <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2023-12-08 14:57:49 Re: Postgres storage migration
Previous Message ROHIT SACHDEVA 2023-12-08 13:59:56 Re: Related to Foreign Table Accessing