On 19 July 2011 03:44, Simon Riggs <si...@2ndquadrant.com> wrote:
> Cascading replication feature for streaming log-based replication.
> Standby servers can now have WALSender processes, which can work with
> either WALReceiver or archive_commands to pass data. Fully updated
> docs, including new conceptual terms of sending server, upstream and
> downstream servers. WALSenders terminated when promote to master.
>
> Fujii Masao, review, rework and doc rewrite by Simon Riggs
I've only just started looking at this.
In doc/src/sgml/config.sgml:
Note that in addition to these parameters,
<xref linkend="guc-wal-level"> must be set appropriately on the master
server, and may also want to enable WAL archiving as
well (see <xref linkend="runtime-config-wal-archiving">).
s/and may also/and you may also/
In doc/src/sgml/high-availability.sgml:
s/effected/affected/
Also: "i.e., set max_wal_senders, hot_standby and authentication option"
Doesn't sound right. Perhaps something like "... and configure
host-based authentication"
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/
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
