Anyway, moving on: I'd like to hear from y'all about what kind of Postgres replication you think is safest. Patroni, perhaps?
-
-
This is the behaviour of PostgreSQL and there is no good and reliable way to overcome it.
-
I believe you! What about... commercial offerings? Vertica, perhaps?
- 8 more replies
New conversation -
-
-
Postgres is well within its guarantees that "the application will not receive explicit acknowledgment of the successful commit of a transaction until the WAL data is known to be safely received by all the synchronous standbys."
-
This is a subtle point, and I don't think I understand it well! Do you think that means Postgres+Patroni still satisfies SI (or SSI)?
- 3 more replies
New conversation -
-
-
The nuance here is that if a commit returns under synchronous replication it will be multi-node durable, but visibility does not guarantee durability because cancelled commit waits will make the transaction visible immediately.
-
This kinda sounds like it could manifest as aborted reads, which would be an SI violation, right?
- 1 more reply
New conversation -
-
-
No, there aren’t any, why is this a surprise?
-
(As long as the context is on-prem software)
End of conversation
New conversation -
-
-
The builtin replication also has different tx visibility ordering on master and standby. Master visibility order is based on active transaction list update order, standby is based on transaction log order. They can be significantly different, esp. with async commits mixed in.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
CockroachDB implements the PostgreSQL SQL dialect and wire protocol. Does that count?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.