On Sun, Sep 15, 2019 at 04:37:18PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/different-replication-solutions.html
> Description:
>
> Not sure if this is an error but I was wondering about this sentence: "In
> fact, write performance is often worse than that of a single server". Isn't
> syncronous multimaster write performance always (rather than "often") worse
> than that of a single (non-distributed) server?
Very good point. I have improved the text with the attached patch. I
also clarified the asynchronous case.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
new file mode 100644
index 43bcb2a..a42541f
*** a/doc/src/sgml/high-availability.sgml
--- b/doc/src/sgml/high-availability.sgml
*************** protocol to make nodes agree on a serial
*** 237,243 ****
<listitem>
<para>
! For servers that are not regularly connected, like laptops or
remote servers, keeping data consistent among servers is a
challenge. Using asynchronous multimaster replication, each
server works independently, and periodically communicates with
--- 237,244 ----
<listitem>
<para>
! 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
server works independently, and periodically communicates with
*************** protocol to make nodes agree on a serial
*** 256,264 ****
In synchronous multimaster 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 shared disk
to reduce the communication overhead. Synchronous multimaster
replication is best for mostly read workloads, though its big
--- 257,264 ----
In synchronous multimaster 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
replication is best for mostly read workloads, though its big
