|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.19 2007/11/0819:18:23 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.20 2007/11/0822:08:18 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability"> |
4 | 4 | <title>High Availability, Load Balancing, and Replication</title> |
|
106 | 106 | </varlistentry> |
107 | 107 |
|
108 | 108 | <varlistentry> |
109 | | - <term>File System Replication</term> |
| 109 | + <term>File System(Block-Device)Replication</term> |
110 | 110 | <listitem> |
111 | 111 |
|
112 | 112 | <para> |
@@ -192,7 +192,8 @@ protocol to make nodes agree on a serializable transactional order. |
192 | 192 | using two-phase commit (<xref linkend="sql-prepare-transaction" |
193 | 193 | endterm="sql-prepare-transaction-title"> and <xref |
194 | 194 | linkend="sql-commit-prepared" endterm="sql-commit-prepared-title">. |
195 | | - Pgpool and Sequoia are an example of this type of replication. |
| 195 | + Pgpool and Sequoia are an example of this type of replication. |
| 196 | + This can be implemented using the PL/Proxy toolset as well. |
196 | 197 | </para> |
197 | 198 | </listitem> |
198 | 199 | </varlistentry> |
|