|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.23 2007/11/10 19:14:02 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.24 2007/11/10 19:19:36 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability"> |
4 | 4 | <title>High Availability, Load Balancing, and Replication</title> |
@@ -405,12 +405,12 @@ protocol to make nodes agree on a serializable transactional order. |
405 | 405 | <para> |
406 | 406 | Many of the above solutions allow multiple servers to handle multiple |
407 | 407 | queries, but none allow a single query to use multiple servers to |
408 | | - complete faster. This allows multiple servers to work concurrently |
409 | | - on a single query.This is usually accomplished by splitting the |
410 | | - data among servers and having each server execute its part of the |
411 | | - query and return results to a central server where they are combined |
412 | | - and returned to the user. <productname>Pgpool-II</> has this |
413 | | - capability. Also, this can be implemented using the |
| 408 | + complete faster. Thissolutionallows multiple servers to work |
| 409 | +concurrentlyon a single query.It is usually accomplished by |
| 410 | +splitting thedata among servers and having each server execute its |
| 411 | +part of thequery and return results to a central server where they |
| 412 | +are combinedand returned to the user. <productname>Pgpool-II</> |
| 413 | +has thiscapability. Also, this can be implemented using the |
414 | 414 | <productname>PL/Proxy</> toolset. |
415 | 415 | </para> |
416 | 416 |
|
|