From e1693e514c197b6ddd27b59678f78b9385ac0539 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 17 Nov 2006 16:38:44 +0000 Subject: [PATCH] Rename replication section "High Availability and Load Balancing". --- doc/src/sgml/filelist.sgml | 4 +- .../{failover.sgml => high-availability.sgml} | 43 ++++++++++--------- doc/src/sgml/postgres.sgml | 4 +- 3 files changed, 27 insertions(+), 24 deletions(-) rename doc/src/sgml/{failover.sgml => high-availability.sgml} (86%) diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml index 945b08375f..fe1fdfd579 100644 --- a/doc/src/sgml/filelist.sgml +++ b/doc/src/sgml/filelist.sgml @@ -1,4 +1,4 @@ - + @@ -34,7 +34,7 @@ - + diff --git a/doc/src/sgml/failover.sgml b/doc/src/sgml/high-availability.sgml similarity index 86% rename from doc/src/sgml/failover.sgml rename to doc/src/sgml/high-availability.sgml index 29d770c73e..56733e38e8 100644 --- a/doc/src/sgml/failover.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1,35 +1,38 @@ - + - - Failover, Replication, Load Balancing, and Clustering Options + + High Availability and Load Balancing + high availability failover replication load balancing clustering + data partitioning Database servers can work together to allow a second server to - quickly take over if the primary server fails (failover), or to - allow several computers to serve the same data (load balancing). - Ideally, database servers could work together seamlessly. Web - servers serving static web pages can be combined quite easily by - merely load-balancing web requests to multiple machines. In - fact, read-only database servers can be combined relatively easily - too. Unfortunately, most database servers have a read/write mix - of requests, and read/write servers are much harder to combine. - This is because though read-only data needs to be placed on each - server only once, a write to any server has to be propagated to - all servers so that future read requests to those servers return - consistent results. + quickly take over quickly if the primary server fails (high + availability), or to allow several computers to serve the same + data (load balancing). Ideally, database servers could work + together seamlessly. Web servers serving static web pages can + be combined quite easily by merely load-balancing web requests + to multiple machines. In fact, read-only database servers can + be combined relatively easily too. Unfortunately, most database + servers have a read/write mix of requests, and read/write servers + are much harder to combine. This is because though read-only + data needs to be placed on each server only once, a write to any + server has to be propagated to all servers so that future read + requests to those servers return consistent results. - This synchronization problem is the fundamental difficulty for servers - working together. Because there is no single solution that eliminates - the impact of the sync problem for all use cases, there are multiple - solutions. Each solution addresses this problem in a different way, and - minimizes its impact for a specific workload. + This synchronization problem is the fundamental difficulty for + servers working together. Because there is no single solution + that eliminates the impact of the sync problem for all use cases, + there are multiple solutions. Each solution addresses this + problem in a different way, and minimizes its impact for a specific + workload. diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml index bba2bcd601..4f55c2dcac 100644 --- a/doc/src/sgml/postgres.sgml +++ b/doc/src/sgml/postgres.sgml @@ -1,4 +1,4 @@ - +