|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.21 2007/11/08 22:14:18 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.22 2007/11/09 16:36:04 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability"> |
4 | 4 | <title>High Availability, Load Balancing, and Replication</title> |
@@ -193,7 +193,6 @@ protocol to make nodes agree on a serializable transactional order. |
193 | 193 | endterm="sql-prepare-transaction-title"> and <xref |
194 | 194 | linkend="sql-commit-prepared" endterm="sql-commit-prepared-title">. |
195 | 195 | Pgpool and Sequoia are an example of this type of replication. |
196 | | - Also, this can be implemented using the PL/Proxy toolset. |
197 | 196 | </para> |
198 | 197 | </listitem> |
199 | 198 | </varlistentry> |
@@ -408,7 +407,7 @@ protocol to make nodes agree on a serializable transactional order. |
408 | 407 | accomplished by splitting the data among servers and having each server |
409 | 408 | execute its part of the query and return results to a central server |
410 | 409 | where they are combined and returned to the user. Pgpool-II has this |
411 | | - capability. |
| 410 | + capability. Also, this can be implemented using the PL/Proxy toolset. |
412 | 411 | </para> |
413 | 412 |
|
414 | 413 | </chapter> |