Re: Set fallback_application_name for a walreceiver to cluster_name

2019-02-27 Thread Peter Eisentraut
On 2019-02-21 01:36, Euler Taveira wrote: >> By default, the fallback_application_name for a physical walreceiver is >> "walreceiver". This means that multiple standbys cannot be >> distinguished easily on a primary, for example in pg_stat_activity or >> synchronous_standby_names. >> > Although st

Re: Set fallback_application_name for a walreceiver to cluster_name

2019-02-20 Thread Euler Taveira
Em sex, 8 de fev de 2019 às 05:16, Peter Eisentraut escreveu: > > By default, the fallback_application_name for a physical walreceiver is > "walreceiver". This means that multiple standbys cannot be > distinguished easily on a primary, for example in pg_stat_activity or > synchronous_standby_name

Set fallback_application_name for a walreceiver to cluster_name

2019-02-08 Thread Peter Eisentraut
e-6f1b-d5ba-4957ff40f...@2ndquadrant.com> -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services From b2901f54e943f6b609a93890c682aa9cf416e3c1 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 8 Feb 2019 0