Re: BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master - Mailing list pgsql-bugs

From Sergei Kornilov
Subject Re: BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master
Date
Msg-id 4325811583763530@vla5-dcf36e533bf7.qloud-c.yandex.net
Whole thread Raw
In response to BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16288: application_name from client's primary_conninfo notset in pg_stat_replication on master
List pgsql-bugs
Hello

Works for me.
Please share results of such queries:

select * from pg_stat_wal_receiver;
select * from pg_file_settings where name = 'primary_conninfo';

Cluster name will be used as fallback application name when no application_name was provided. I think you have several
primary_conninfo,one of which is in postgresql.auto.conf that was created by pg_basebackup -R
 

regards, Sergei



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master
Next
From: Andreas Ntaflos
Date:
Subject: Re: BUG #16288: application_name from client's primary_conninfo notset in pg_stat_replication on master