Re:Select ’Hello, World’: Serverless Postgres Built for the ...
by throwaway892238 on Thursday June 16, 2022 @09:59AM
(#31766125)
But the manual intervention of conflict resolution in a Git repo is done in a working tree. The named branch's HEAD remains the same until the conflict has been resolved and the commit is merged/pushed. So nobody sees the conflict at all, they only ever see either the old code, or the merged resolved code.
Re:Select ’Hello, World’: Serverless Postgres Built for the ...
by ledauphin on Wednesday June 15, 2022 @11:33PM
(#31762211)
I've been wondering if it makes sense for databases to start offering CRDTs natively, so that you can perform merges that are algorithmically conflict-free.
Re:Select ’Hello, World’: Serverless Postgres Built for the ...
by mattashii on Thursday June 16, 2022 @02:37AM
(#31763080)
In a sense, a CRTD is a database. But the 'conflict-free' is only because it defines semantics for conflicting operations.
But, because SQL has conflict resolution by cancellation of one of the two conflicting modifications, I don't think that it is reasonable (or even possible) to merge 2 divergent databases in a single way that always conforms to the needs of the developer and/or application.
Re:Select ’Hello, World’: Serverless Postgres Built for the ...
by nikita on Thursday June 16, 2022 @02:32AM
(#31763045)
CRDTs are pretty hard to implement at the Neon storage level - pages don’t know what’s written on them. I don’t know of a general purpose database that supports CRDTs. It would be cool though!
Doing so for a database seems less desirable from an availability perspective, especially with high-throughput databases.