Re: walreceiver fallback_application_name - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: walreceiver fallback_application_name
Date
Msg-id m27he4bmec.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: walreceiver fallback_application_name  (Magnus Hagander <magnus@hagander.net>)
Responses Re: walreceiver fallback_application_name  (Robert Haas <robertmhaas@gmail.com>)
Re: walreceiver fallback_application_name  (Bernd Helmle <mailings@oopsware.de>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Is "walreceiver" something that "the average DBA" is going to realize
> what it is? Perhaps go for something like "replication slave"?

I think walreceiver is very good here, and the user is already
confronted to such phrasing.
 http://www.postgresql.org/docs/9.0/interactive/runtime-config-wal.html#GUC-MAX-WAL-SENDERS

Also, we're about to extend the technique usage in some other places
such as integrated base backup facility and default archiving solution,
so let's talk about what it's doing, not what for.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pg_stat_replication security
Next
From: Josh Berkus
Date:
Subject: Re: replication and pg_hba.conf