Re:Waiting for PostgreSQL 14 – SEARCH and CYCLE clauses
by jd_mongodb on Thursday February 04, 2021 @07:34PM
(#26031589)
FYI: Same report update:
2020-05-26: MongoDB identified a bug in the transaction retry mechanism which they believe was responsible for the anomalies observed in this report; a patch is scheduled for 4.2.8.
Re:Waiting for PostgreSQL 14 – SEARCH and CYCLE clauses
by gqewogpdqa on Thursday February 04, 2021 @07:57PM
(#26031779)
Lots of databases have transaction bugs which they hurriedly rush out patches to. MySQL, Oracle, SQL*Server, even the cloud databases like DynamoDB, CosmosDB, Aurora. Looks like MongoDB fixed this one.
Re:Waiting for PostgreSQL 14 – SEARCH and CYCLE clauses
by justinclift on Thursday February 04, 2021 @08:12PM
(#26031874)
Cool. Hopefully that means it passes the next round of Jepson testing. :)
Re:Waiting for PostgreSQL 14 – SEARCH and CYCLE clauses
by gqewogpdqa on Sunday February 07, 2021 @03:47PM
(#26058056)
Indeed! That would be a great confirmation.
> Jepsen evaluated MongoDB version 4.2.6, and found that even at the strongest levels of read and write concern, it failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations.
I would not use that where data integrity is mission critical.
[0] https://jepsen.io/analyses/mongodb-4.2.6