]> granicus.if.org Git - postgresql/commit
Set fallback_application_name for a walreceiver to cluster_name
authorPeter Eisentraut <peter@eisentraut.org>
Fri, 8 Feb 2019 07:17:21 +0000 (08:17 +0100)
committerPeter Eisentraut <peter@eisentraut.org>
Wed, 27 Feb 2019 09:59:25 +0000 (10:59 +0100)
commit6ae578a91e653ce3f4cba8cab96ce41e0cc7103f
tree6b72d6f6e587f82ebbe2dcf4aecb39181146a9b7
parent414a9d3cf34c7aff1c63533df4c40ebb63bd0840
Set fallback_application_name for a walreceiver to cluster_name

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.

If cluster_name is set, use that for fallback_application_name in the
walreceiver.  (If it's not set, it remains "walreceiver".)  If someone
set cluster_name to identify their instance, we might as well use that
by default to identify the node remotely as well.  It's still possible
to specify another application_name in primary_conninfo explicitly.

Reviewed-by: Euler Taveira <euler@timbira.com.br>
Discussion: https://www.postgresql.org/message-id/flat/1257eaee-4874-e791-e83a-46720c72cac7@2ndquadrant.com
doc/src/sgml/config.sgml
src/backend/replication/walreceiver.c