Re: BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: "daff(at)ptmx(dot)at" <daff(at)ptmx(dot)at>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master
Date: 2020-03-09 14:31:18
Message-ID: 4325811583763530@vla5-dcf36e533bf7.qloud-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andreas Ntaflos 2020-03-09 15:21:55 Re: BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master
Previous Message PG Bug reporting form 2020-03-09 12:24:14 BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master