Re: pgsql: Cascading replication feature for streaming log-based replicatio

On 10 October 2011 15:18, Robert Haas <robertmhaas@gmail.com> wrote:
> On Sat, Oct 8, 2011 at 8:59 AM, Thom Brown <thom@linux.com> wrote:
>> s/and may also/and you may also/
>
> This was already fixed in a later commit.
>
>> In doc/src/sgml/high-availability.sgml:
>>
>> s/effected/affected/
>
> I fixed this.
>
>> Also: "i.e., set max_wal_senders, hot_standby and authentication option"
>>
>> Doesn't sound right.  Perhaps something like "... and configure
>> host-based authentication"
>
> I reworded this.  See what you think.
>
>> In src/backend/postmaster/postmaster.c:
>>
>> (errmsg("terminating walsender all processes to force cascaded"
>>        "standby(s) to update timeline and reconnect")));
>>
>> s/walsender all/all walsender/
>
> This has also been subsequently fixed.  Nothing to see here, folks.

Ah, didn't spot that some of this had already been addressed.  Looks
good to me.  Cheers.

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company