Re: pgsql: Cascading replication feature for streaming log-based replicatio
От | Thom Brown |
---|---|
Тема | Re: pgsql: Cascading replication feature for streaming log-based replicatio |
Дата | |
Msg-id | CAA-aLv4Fs+YywoHjN20aPWn0kMe7jOsM65wVC9ZicQz2VutacQ@mail.gmail.com обсуждение исходный текст |
Ответ на | pgsql: Cascading replication feature for streaming log-based replicatio (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: pgsql: Cascading replication feature for streaming
log-based replicatio
|
Список | pgsql-committers |
On 19 July 2011 03:44, Simon Riggs <simon@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
В списке pgsql-committers по дате отправления: