From b035722f2994f085bdbf74e66e2f8045ad9ca816 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 22 Nov 2006 18:14:26 +0000 Subject: [PATCH] Update HA docs with more wording improvements. --- doc/src/sgml/high-availability.sgml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index bc672e5655..bfedcb8c04 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1,4 +1,4 @@ - + High Availability and Load Balancing @@ -205,9 +205,9 @@ protocol to make nodes agree on a serializable transactional order. - PostgreSQL does not offer this type of load - balancing, though PostgreSQL two-phase commit - (PostgreSQL does not offer this type of replication, + though PostgreSQL two-phase commit ( and ) can be used to implement this in application code or middleware. @@ -252,7 +252,8 @@ protocol to make nodes agree on a serializable transactional order. - This allows multiple servers to work concurrently on a single + Many of the above solutions allow multiple servers handle multiple sessions, but none allow a single query to use +multiple server to complete fas to This allows multiple servers to work concurrently on a single query. One possible way this could work is for the data to be split among servers and for each server to execute its part of the query and results sent to a central server to be combined -- GitLab