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

From: Thom Brown <thom(at)linux(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Cascading replication feature for streaming log-based replicatio
Date: 2011-10-08 12:59:45
Message-ID: CAA-aLv4Fs+YywoHjN20aPWn0kMe7jOsM65wVC9ZicQz2VutacQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 19 July 2011 03:44, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2011-10-08 14:41:27 pgsql: Fix brain fade in cost estimation for index-only scans.
Previous Message Cédric Villemain 2011-10-08 10:40:03 Re: pgsql: Support index-only scans using the visibility map to avoid heap

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-10-08 14:31:14 Re: pg_upgrade - add config directory setting
Previous Message Jeff Davis 2011-10-08 09:01:29 Re: GiST for range types (was Re: Range Types - typo + NULL string constructor)