Aside: I would like to read a Jepsen analysis of CedarDB. They have some academic cred and make some big claims. I hope they pay for a Jepsen analysis sometime soon.
On-topic: What a mess. MySQL performed badly unreplicated[1], and Galera's claims are a mix of unlikely and impossible, so I am not very surprised, but, still. Good to have it documented and maybe Galera will be improved and its documentation corrected.
Keep in mind CedarDB is a single node system so while they still of course may be doing transactions incorrectly (as anyone might) it probably won't be quite as fun (nor quite as risky) as the mistakes you might find in distributed transactions.
<sigh> I woke up this morning and saw that too. I think I actually introduced that as a text-editor fat-finger when merging fixes from my human editor--mistakes, it's safe to assume, are mine alone. Thanks for the heads-up. :-)
cyplo | 5 hours ago
Thank you @aphyr ! You're always so generous with your time and lending your skills to the community ! :)
[OP] aphyr | an hour ago
Thanks for reading! <3
cmcaine | 3 hours ago
Aside: I would like to read a Jepsen analysis of CedarDB. They have some academic cred and make some big claims. I hope they pay for a Jepsen analysis sometime soon.
On-topic: What a mess. MySQL performed badly unreplicated[1], and Galera's claims are a mix of unlikely and impossible, so I am not very surprised, but, still. Good to have it documented and maybe Galera will be improved and its documentation corrected.
eatonphil | 3 hours ago
Keep in mind CedarDB is a single node system so while they still of course may be doing transactions incorrectly (as anyone might) it probably won't be quite as fun (nor quite as risky) as the mistakes you might find in distributed transactions.
cmcaine | 2 hours ago
Sure, but Jepsen regularly finds bugs in single-node databases too.
eatonphil | 2 hours ago
Sure, I was a big fan of the 2023 MySQL report.
eatonphil | 3 hours ago
This was a particularly easy to read report, well done!
Little typo here ("provide" as "provi..")
[OP] aphyr | 2 hours ago
<sigh> I woke up this morning and saw that too. I think I actually introduced that as a text-editor fat-finger when merging fixes from my human editor--mistakes, it's safe to assume, are mine alone. Thanks for the heads-up. :-)