diff options
| author | Bruce Momjian <bruce@momjian.us> | 2006-11-22 04:00:19 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2006-11-22 04:00:19 +0000 |
| commit | 3b0313580e8450eba6ca6ca4b440f9d8f5a3273e (patch) | |
| tree | a915fff031ea7ff485237bf3b29842a754533d6e | |
| parent | ffa0e8f0cdc1f25745eb8b09bfdfdc5b385f7df8 (diff) | |
| download | postgresql-3b0313580e8450eba6ca6ca4b440f9d8f5a3273e.tar.gz postgresql-3b0313580e8450eba6ca6ca4b440f9d8f5a3273e.zip | |
New async/sync multi-master headings for docs.
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index ba7f2e2d9fd..bc09f40c584 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1,4 +1,4 @@ -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.9 2006/11/22 03:44:52 momjian Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.10 2006/11/22 04:00:19 momjian Exp $ --> <chapter id="high-availability"> <title>High Availability and Load Balancing</title> @@ -184,22 +184,22 @@ protocol to make nodes agree on a serializable transactional order. </varlistentry> <varlistentry> - <term>Multi-Master Clustering</term> + <term>Multi-Master Replication</term> <listitem> <para> - In clustering, 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, 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. 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, + In multi-master 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, 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. 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 <function>random()</>. </para> @@ -246,7 +246,7 @@ protocol to make nodes agree on a serializable transactional order. </varlistentry> <varlistentry> - <term>Clustering For Parallel Query Execution</term> + <term>Multi-Server Parallel Query Execution</term> <listitem> <para> |