Re: synchronized standby: committed local and waiting for remote ack

2023-01-16 Thread qihua wu
How to understand "because you could easily get into a situation where *none* of the nodes represent truth."? In current design, when a user commits, it will first commit on primary, and then is waiting for slave ack. if slaves and primary are splitted in the network, then the user commit command

Re: synchronized standby: committed local and waiting for remote ack

2023-01-13 Thread Tom Lane
qihua wu writes: > We are using patroni to set up 1 primary and 5 slaves, and using ANY 2 (*) > to commit a transaction if any 2 standbys receive the WAL. If there is a > network partitioning between the primary and the slave, then commit will > hang from user perspective, but the commit is actual

synchronized standby: committed local and waiting for remote ack

2023-01-13 Thread qihua wu
We are using patroni to set up 1 primary and 5 slaves, and using ANY 2 (*) to commit a transaction if any 2 standbys receive the WAL. If there is a network partitioning between the primary and the slave, then commit will hang from user perspective, but the commit is actually done locally, just wait