Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 74F8A143B1AD for ; Tue, 20 Mar 2012 18:26:57 -0300 (ADT) Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SA6Zz-0007EF-Me for pgsql-docs@postgresql.org; Tue, 20 Mar 2012 21:26:56 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1SA6Zn-0001Dn-3z for pgsql-docs@postgresql.org; Tue, 20 Mar 2012 17:26:43 -0400 Date: Tue, 20 Mar 2012 17:26:43 -0400 From: Bruce Momjian To: PostgreSQL-documentation Subject: Replication docs update Message-ID: <20120320212643.GA4599@momjian.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="9amGYk9869ThD9tj" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201203/9 X-Sequence-Number: 7208 --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Our chapter, "Comparison of Different Solutions", needs an update to use our new streaming replication terminology, and an update to mention the synchronous option. Patch attached. I would like to apply it to head and 9.1. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + --9amGYk9869ThD9tj Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="repl_doc.diff" diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml new file mode 100644 index ed34dac..e4f2e01 *** a/doc/src/sgml/high-availability.sgml --- b/doc/src/sgml/high-availability.sgml *************** protocol to make nodes agree on a serial *** 140,146 **** ! Warm and Hot Standby Using Point-In-Time Recovery (PITR) --- 140,146 ---- ! Transaction Log Shipping *************** protocol to make nodes agree on a serial *** 148,158 **** stream of write-ahead log (WAL) records. If the main server fails, the standby contains almost all of the data of the main server, and can be quickly ! made the new master database server. This is asynchronous and ! can only be done for the entire database server. ! A PITR standby server can be implemented using file-based log shipping () or streaming replication (see ), or a combination of both. For information on hot standby, see . --- 148,158 ---- stream of write-ahead log (WAL) records. If the main server fails, the standby contains almost all of the data of the main server, and can be quickly ! made the new master database server. This can be synchronous or ! asynchronous and can only be done for the entire database server. ! A standby server can be implemented using file-based log shipping () or streaming replication (see ), or a combination of both. For information on hot standby, see . *************** protocol to make nodes agree on a serial *** 291,297 **** Feature Shared Disk Failover File System Replication ! Hot/Warm Standby Using PITR Trigger-Based Master-Standby Replication Statement-Based Replication Middleware Asynchronous Multimaster Replication --- 291,297 ---- Feature Shared Disk Failover File System Replication ! Transaction Log Shipping Trigger-Based Master-Standby Replication Statement-Based Replication Middleware Asynchronous Multimaster Replication *************** protocol to make nodes agree on a serial *** 305,311 **** Most Common Implementation NAS DRBD ! PITR Slony pgpool-II Bucardo --- 305,311 ---- Most Common Implementation NAS DRBD ! Streaming Repl. Slony pgpool-II Bucardo *************** protocol to make nodes agree on a serial *** 360,366 **** No waiting for multiple servers • ! • • • --- 360,366 ---- No waiting for multiple servers • ! with sync off • • *************** protocol to make nodes agree on a serial *** 371,377 **** Master failure will never lose data • • ! • --- 371,377 ---- Master failure will never lose data • • ! with sync on • *************** protocol to make nodes agree on a serial *** 382,388 **** Standby accept read-only queries ! Hot only • • • --- 382,388 ---- Standby accept read-only queries ! with hot • • • --9amGYk9869ThD9tj--