From: Tatsuo Ishii Date: Thu, 30 Jul 2020 23:04:26 +0000 (+0900) Subject: Doc: fix high availability solutions comparison. X-Git-Tag: REL9_5_23~10 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9baf5d639261d72a2f86311fde93f612f7ede9dc;p=thirdparty%2Fpostgresql.git 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 --- diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 25b7e30449e..a15e544eb52 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -404,7 +404,7 @@ protocol to make nodes agree on a serializable transactional order. • • • - + • • @@ -446,9 +446,8 @@ 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 - PL/Proxy tool set. + are combined and returned to the user. This can be implemented using the + PL/Proxy tool set.