From ec9bc191e2bbe41c43a9483bf20f3eed242045c5 Mon Sep 17 00:00:00 2001 From: Andres Freund Date: Mon, 15 Jun 2020 10:39:15 -0700 Subject: [PATCH v1 8/8] docs: WIP multi-master rephrasing. Perhaps active-active would be a better term? Author: Reviewed-By: Discussion: https://postgr.es/m/ Backpatch: --- doc/src/sgml/high-availability.sgml | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 6a9184f314e..198fd5b66ed 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -38,10 +38,10 @@ Some solutions deal with synchronization by allowing only one server to modify the data. Servers that can modify data are - called read/write, master or primary servers. - Servers that track changes in the master are called standby + called read/write, primary (or master) servers. + Servers that track changes in the primary are called standby or secondary servers. A standby server that cannot be connected - to until it is promoted to a master server is called a warm + to until it is promoted to a primary server is called a warm standby server, and one that can accept connections and serves read-only queries is called a hot standby server. @@ -177,14 +177,14 @@ protocol to make nodes agree on a serializable transactional order. - Trigger-Based Master-Standby Replication + Trigger-Based Primary-Standby Replication - A master-standby replication setup sends all data modification - queries to the master server. The master server asynchronously + A primary-standby replication setup sends all data modification + queries to the primary server. The primary server asynchronously sends data changes to the standby server. The standby can answer - read-only queries while the master server is running. The + read-only queries while the primary server is running. The standby server is ideal for data warehouse queries. @@ -233,14 +233,14 @@ protocol to make nodes agree on a serializable transactional order. - Asynchronous Multimaster Replication + Asynchronous Multi-Source Replication For servers that are not regularly connected or have slow communication links, like laptops or remote servers, keeping data consistent among servers is a - challenge. Using asynchronous multimaster replication, each + challenge. Using asynchronous multi-source replication, each server works independently, and periodically communicates with the other servers to identify conflicting transactions. The conflicts can be resolved by users or conflict resolution rules. @@ -250,17 +250,17 @@ protocol to make nodes agree on a serializable transactional order. - Synchronous Multimaster Replication + Synchronous Multi-Source Replication - In synchronous multimaster replication, each server can accept + In synchronous multi-source replication, each server can accept write requests, and modified data is transmitted from the original server to every other server before each transaction commits. Heavy write activity can cause excessive locking and commit delays, leading to poor performance. Read requests can be sent to any server. Some implementations use shared disk - to reduce the communication overhead. Synchronous multimaster + to reduce the communication overhead. Synchronous multi-source replication 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 primary and @@ -351,7 +351,7 @@ protocol to make nodes agree on a serializable transactional order. - Allows multiple master servers + Allows multiple primary servers -- 2.25.0.114.g5b0ca878e0