From a63fbd34813ea61a3d293e1143e509378aa9d6e7 Mon Sep 17 00:00:00 2001 From: Tatsuo Ishii Date: Fri, 31 Jul 2020 07:48:23 +0900 Subject: [PATCH] Doc: fix high availability solutions comparison. In "High Availability, Load Balancing, and Replication" chapter, certain descriptions of Pgpool-II were not correct at this point. It does not need conflict resolution. Also "Multiple-Server Parallel Query Execution" is not supported anymore. Discussion: https://postgr.es/m/20200726.230128.53842489850344110.t-ishii%40sraoss.co.jp Author: Tatsuo Ishii Reviewed-by: Bruce Momjian Backpatch-through: 9.5 --- doc/src/sgml/high-availability.sgml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index a42541f4200..4ad5a8b9508 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -433,7 +433,7 @@ protocol to make nodes agree on a serializable transactional order. • • - + • • @@ -475,8 +475,7 @@ protocol to make nodes agree on a serializable transactional order. concurrently on a single query. It is usually accomplished by splitting the data among servers and having each server execute its part of the query and return results to a central server where they - are combined and returned to the user. Pgpool-II - has this capability. Also, this can be implemented using the + are combined and returned to the user. This can be implemented using the PL/Proxy tool set.