News for hackers. Stuff that matters.
Re:OrioleDB – solving some PostgreSQL wicked problems by akorotkov on Friday February 25, 2022 @12:47AM (#30464070)
Right. The idea of active-active OrioleDB multimaster is to apply changes locally and in parallel send it to the leader. Then sync on commit and ensure there is no conflicts.

The design document will be published later.

Re:OrioleDB – solving some PostgreSQL wicked problems by otterley on Friday February 25, 2022 @02:05AM (#30464434)
Please have it subjected to a Jepsen test suite ASAP!
Re:OrioleDB – solving some PostgreSQL wicked problems by carlhjerpe on Friday February 25, 2022 @05:27AM (#30465722)
My thinking is since it's postgres wire compatible the existing tests should work?
Re:OrioleDB – solving some PostgreSQL wicked problems by yencabulator on Wednesday March 02, 2022 @09:01PM (#30536195)
Jepsen does much more than basic end-to-end tests, including intentionally partitioning the cluster. Tests written for a non-distributed system are downright friendly compared to what Jepsen does to distributed systems.
Re:OrioleDB – solving some PostgreSQL wicked problems by k__ on Friday February 25, 2022 @05:55AM (#30465883)
Does Jepsen just run automated tests?
Re:OrioleDB – solving some PostgreSQL wicked problems by carlhjerpe on Friday February 25, 2022 @06:03AM (#30465945)
I mean they're automated but also hand crafted.

https://github.com/jepsen-io/jepsen

Re:OrioleDB – solving some PostgreSQL wicked problems by collegeburner on Friday February 25, 2022 @09:48AM (#30467823)
Those are very expensive and booked months in advance. Aphyr sometimes comments on HN and is of course a better source on this but that's what I recall reading.
Re:OrioleDB – solving some PostgreSQL wicked problems by otterley on Friday February 25, 2022 @10:29AM (#30468274)
It’s the price you pay to reassure customers that your newfangled distributed database won’t experience data loss or inconsistency.