From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Cascading replication feature for streaming log-based replicatio |
Date: | 2011-10-10 14:18:08 |
Message-ID: | CA+TgmobapeewxFm9byPB0dO+3UpmkExmmmFrMhqhcMhr-QtUPw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Sat, Oct 8, 2011 at 8:59 AM, Thom Brown <thom(at)linux(dot)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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-10-10 14:20:17 | Re: pgsql: Cascading replication feature for streaming log-based replicatio |
Previous Message | Robert Haas | 2011-10-10 14:17:08 | pgsql: Some minor wordsmithing for the cascading replication documentat |
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-10-10 14:20:17 | Re: pgsql: Cascading replication feature for streaming log-based replicatio |
Previous Message | Robert Haas | 2011-10-10 14:01:51 | ALTER EXTENSION .. ADD/DROP weirdness |