Re: application_name backend (not) reporting back to the client : pgbouncer, PgSQL 16.1, pgbouncer 1.21.0 - Mailing list pgsql-admin

From Tom Lane
Subject Re: application_name backend (not) reporting back to the client : pgbouncer, PgSQL 16.1, pgbouncer 1.21.0
Date
Msg-id 1750352.1702159733@sss.pgh.pa.us
Whole thread Raw
In response to Re: application_name backend (not) reporting back to the client : pgbouncer, PgSQL 16.1, pgbouncer 1.21.0  (Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>)
Responses Re: application_name backend (not) reporting back to the client : pgbouncer, PgSQL 16.1, pgbouncer 1.21.0
List pgsql-admin
Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com> writes:
> Hi again, I am puzzled with your observations, this is what I get with
> psql straight against PostgreSQL no pgbouncer involved :

> command :
> psql "postgresql://amantzio@localhost:5432/dynacom?application_name="

> ...
>
public.S....is_superuser.on.S....application_name..S...&default_transaction_read_only.off.S....scram_iterations.4096.S....DateStyle.ISO,

                              ^^^^^^^^^^^^^^^^^^^^^^^

I see the report of application_name with an empty-string value right
there.

> the client does not send the application_name

I do not know what you mean by that, but maybe your client code has
some special-case behavior for an empty string?

            regards, tom lane



pgsql-admin by date:

Previous
From: Achilleas Mantzios
Date:
Subject: Re: application_name backend (not) reporting back to the client : pgbouncer, PgSQL 16.1, pgbouncer 1.21.0
Next
From: Achilleas Mantzios
Date:
Subject: Re: application_name backend (not) reporting back to the client : pgbouncer, PgSQL 16.1, pgbouncer 1.21.0