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

Поиск
Список
Период
Сортировка
От Sergei Kornilov
Тема Re: BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master
Дата
Msg-id 4325811583763530@vla5-dcf36e533bf7.qloud-c.yandex.net
обсуждение исходный текст
Ответ на BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #16288: application_name from client's primary_conninfo notset in pg_stat_replication on master  (Andreas Ntaflos <daff@mailbox.org>)
Список 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 по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #16288: application_name from client's primary_conninfo not set in pg_stat_replication on master
Следующее
От: Andreas Ntaflos
Дата:
Сообщение: Re: BUG #16288: application_name from client's primary_conninfo notset in pg_stat_replication on master