From ffa0e8f0cdc1f25745eb8b09bfdfdc5b385f7df8 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 22 Nov 2006 03:44:52 +0000 Subject: [PATCH] Add mention of shared-memory/disk for multi-master clustering. --- doc/src/sgml/high-availability.sgml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 940261d247..ba7f2e2d9f 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1,4 +1,4 @@ - + High Availability and Load Balancing @@ -193,11 +193,13 @@ protocol to make nodes agree on a serializable transactional order. other server before each transaction commits. Heavy write activity can cause excessive locking, leading to poor performance. In fact, write performance is often worse than that of a single - server. Read requests can be sent to any server. Clustering - is best for mostly read workloads, though its big advantage - is that any server can accept write requests — there is - no need to partition workloads between master and slave servers, - and because the data changes are sent from one server to another, + server. Read requests can be sent to any server. Some + implementations use cluster-wide shared memory or shared disk + to reduce the communication overhead. Clustering is best for + mostly read workloads, though its big advantage is that any + server can accept write requests — there is no need to + partition workloads between master and slave servers, and + because the data changes are sent from one server to another, there is no problem with non-deterministic functions like random(). -- 2.40.0