Re: walreceiver fallback_application_name - Mailing list pgsql-hackers

From Tom Lane
Subject Re: walreceiver fallback_application_name
Date
Msg-id 8386.1295195364@sss.pgh.pa.us
Whole thread Raw
In response to walreceiver fallback_application_name  (Magnus Hagander <magnus@hagander.net>)
Responses Re: walreceiver fallback_application_name  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Since we now show the application name in pg_stat_replication, I think
> it would make sense to have the walreceiver set
> fallback_application_name on the connection string, like so:

Seems reasonable, but "postgres" is a mighty poor choice of name
for that, no?  I don't have any really great substitute suggestion
--- best I can do offhand is "walreceiver" --- but "postgres" seems
uselessly generic, not to mention potentially confusing compared
to the default superuser name for instance.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: replication and pg_hba.conf
Next
From: Tom Lane
Date:
Subject: Re: ToDo List Item - System Table Index Clustering