Re: walreceiver fallback_application_name - Mailing list pgsql-hackers

From Robert Haas
Subject Re: walreceiver fallback_application_name
Date
Msg-id AANLkTi=thPbr7Tr8pg21fdT53avNcDa87Cy9mAFbuMw_@mail.gmail.com
Whole thread Raw
In response to Re: walreceiver fallback_application_name  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: walreceiver fallback_application_name  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Sun, Jan 16, 2011 at 3:53 PM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> 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

I agree that walreceiver is a reasonable default to supply in this case.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Streaming base backups
Next
From: Robert Haas
Date:
Subject: Re: Warning compiling pg_dump (MinGW, Windows XP)