Reputation: 1
When the synchronous_commit parameter is used in standalone and primary/standby modes, are the meanings of the values local and on different?
When the GUC parameter synchronous_commit of the openGauss database is used in standalone and primary/standby modes, are the meanings of the values local and on different?
Upvotes: 0
Views: 49
Answers (1)
Reputation: 23
Yes, about openGauss the meanings of the values local and on are different when the synchronous_commit parameter is used in standalone and primary/standby modes. In standalone mode, the local value means that the transaction is committed locally, while the on value means that the transaction is committed on the primary server. In primary/standby mode, the local value means that the transaction is committed on the primary server, while the on value means that the transaction is committed on both the primary and standby servers.
Upvotes: 0
Related Questions
- Serializable Isolation Level Confusion - Write Skew (Postgres)
- How are the O_SYNC and O_DIRECT flags in open(2) different/alike?
- Concurrently updating a field with READ_COMMITED
- Using a read-only replica in synchronous commit mode, is it possible for a query to get different results on the secondary than the primary?
- does Kafka auto commit is sync or async under the hood?
- What is the practical difference between flush and commit?
- Is Cassandra use two phase commit when config write multi replicas ?
- Why is two-phase commit considered atomic?
- Oozie > what is the difference between asynchronous actions and synchronous actions
- When calling commitOffsets on Kafka high level ConsumerConnector, what value gets committed?