"Note: Because of the way synchronous replication is implemented in PostgreSQL it is still possible to lose transactions even when using synchronous_mode_strict" oh, okay, cool is there a postgres replication/HA setup that *doesn't* lose data? https://github.com/zalando/patroni/blob/master/docs/replication_modes.rst#synchronous-mode …
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I never answer this kind of question, because you might not *need* a replication. Apply KISS to your architecture regarding your RPO and RTO. The less layer you'll have, the less problem you'll encounter.
-
Ah, to be clear, I test distributed database safety properties (https://jepsen.io ), and I'm trying to decide what kind of postgres deployment would be most helpful to evaluate.
End of conversation
New conversation -
-
-
I’m hoping you will take on FoundationDB some day. We could really use a database that passes.
-
If anyone can afford to hire Jepsen for this kind of work, it's Apple. :-)
- 1 more reply
New conversation -
-
-
I think it will be awesome to try out the work onhttps://www.citusdata.com/
-
never had an opportunity to test it seriously but it looks very promising!
- 2 more replies
New conversation -
-
-
It's been a few years since I've been here (9.2 and 9.6 eras), but we ran into a number of crippling issues with synchronous replication for availability that did not seem widely known (at least, at the time).
-
At the time, I recall we dubbed its model "eventually available"
- 1 more reply
New conversation -
-
-
I’m working on https://github.com/citusdata/pg_auto_failover … ; check it out!
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.