Commite4ca62b

committed

docs: Improve A?synchronous Multimaster Replication descr.

The docs for sync and async multimaster replication were unclear aboutwhen to use it, and when it has benefits; this change clarifies that.Reported-by: juha-pekka.eloranta@reaktor.fiDiscussion:https://postgr.es/m/156856543824.1274.12180817186798859836@wrigleys.postgresql.orgBackpatch-through: 9.4

1 parentf68d5bf commite4ca62bCopy full SHA for e4ca62b

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -237,7 +237,8 @@ protocol to make nodes agree on a serializable transactional order.`
`237`	`237`	`<listitem>`
`238`	`238`
`239`	`239`	`<para>`
`240`		`- For servers that are not regularly connected, like laptops or`
	`240`	`+ For servers that are not regularly connected or have slow`
	`241`	`+ communication links, like laptops or`
`241`	`242`	`remote servers, keeping data consistent among servers is a`
`242`	`243`	`challenge. Using asynchronous multimaster replication, each`
`243`	`244`	`server works independently, and periodically communicates with`
`@@ -256,9 +257,8 @@ protocol to make nodes agree on a serializable transactional order.`
`256`	`257`	`In synchronous multimaster replication, each server can accept`
`257`	`258`	`write requests, and modified data is transmitted from the`
`258`	`259`	`original server to every other server before each transaction`
`259`		`- commits. Heavy write activity can cause excessive locking,`
`260`		`- leading to poor performance. In fact, write performance is`
`261`		`- often worse than that of a single server. Read requests can`
	`260`	`+ commits. Heavy write activity can cause excessive locking and`
	`261`	`+ commit delays, leading to poor performance. Read requests can`
`262`	`262`	`be sent to any server. Some implementations use shared disk`
`263`	`263`	`to reduce the communication overhead. Synchronous multimaster`
`264`	`264`	`replication is best for mostly read workloads, though its big`

Comments

(0)