Doc: hack on table 26.1 till it fits in PDF format.

I abbreviated the heck out of the column headings, and made a few
small wording changes, to get it to build warning-free.  I can't
say that the result is pretty, but it's probably better than
removing this table entirely.

As of this commit, we have zero "exceed the available area" warnings
in a US-letter PDF build, and one such warning (about an 863-millipoint
overrun) in an A4 build.  I expect to get rid of that one by renaming
wait events, so I'm not doing anything about it at the formatting
level.

Discussion: https://postgr.es/m/6916.1589146280@sss.pgh.pa.us

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 8862f84412e3b0c059781379bbd9f1392aa4c246..44cc5d2116d257803a9421a13d6f2e6b2cc71e61 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -198,11 +198,11 @@ protocol to make nodes agree on a serializable transactional order.
   
 
   
-   Statement-Based Replication Middleware
+   SQL-Based Replication Middleware
    
 
     
-     With statement-based replication middleware, a program intercepts
+     With SQL-based replication middleware, a program intercepts
      every SQL query and sends it to one or all servers.  Each server
      operates independently.  Read-write queries must be sent to all servers,
      so that every server receives any changes.  But read-only queries can be
@@ -279,19 +279,6 @@ protocol to make nodes agree on a serializable transactional order.
    
   
 
-  
-   Commercial Solutions
-   
-
-    
-     Because PostgreSQL is open source and easily
-     extended, a number of companies have taken PostgreSQL
-     and created commercial closed-source solutions with unique
-     failover, replication, and load balancing capabilities.
-    
-   
-  
-
  
 
  
@@ -302,28 +289,37 @@ protocol to make nodes agree on a serializable transactional order.
  
   High Availability, Load Balancing, and Replication Feature Matrix
   
+   
+   
+   
+   
+   
+   
+   
+   
+   
    
     
      Feature
-     Shared Disk Failover
-     File System Replication
+     Shared Disk
+     File System Repl.
      Write-Ahead Log Shipping
-     Logical Replication
-     Trigger-Based Master-Standby Replication
-     Statement-Based Replication Middleware
-     Asynchronous Multimaster Replication
-     Synchronous Multimaster Replication
+     Logical Repl.
+     Trigger-Based Repl.
+     SQL Repl. Middle-ware
+     Async. MM Repl.
+     Sync. MM Repl.
     
    
 
    
 
     
-     Most common implementations
+     Popular examples
      NAS
      DRBD
-     built-in streaming replication
-     built-in logical replication, pglogical
+     built-in streaming repl.
+     built-in logical repl., pglogical
      Londiste, Slony
      pgpool-II
      Bucardo
@@ -331,7 +327,7 @@ protocol to make nodes agree on a serializable transactional order.
     
 
     
-     Communication method
+     Comm. method
      shared disk
      disk blocks
      WAL
@@ -485,6 +481,14 @@ protocol to make nodes agree on a serializable transactional order.
 
  
 
+  
+   It should also be noted that because PostgreSQL
+   is open source and easily extended, a number of companies have
+   taken PostgreSQL and created commercial
+   closed-source solutions with unique failover, replication, and load
+   balancing capabilities.  These are not discussed here.
+  
+