News for hackers. Stuff that matters.
Re:Show HN: My experimental take on a decentralized ledger by anarazel on Wednesday September 16, 2015 @10:45AM (#10226963)
No. Conccurrency makes it way harder than that.
Re:Show HN: My experimental take on a decentralized ledger by devit on Wednesday September 16, 2015 @01:10PM (#10228157)
In PostgreSQL, you can set the SERIALIZABLE isolation level for the whole database, put a retry loop around all database transactions and completely stop worrying about concurrency issues.

I think all database applications should be written like this at least until performance starts being an issue.

Re:Show HN: My experimental take on a decentralized ledger by anarazel on Wednesday September 16, 2015 @06:38PM (#10230453)
Entirely depends on the the type of workload / application architecture. In some cases the rollback ratios will be massive (I've seen 70%). In other cases adding such a retry loop is unattractive because the latency jitter. Or retaining all involved data for a retry is unattrictive.

Yet Another problem is that you need to enforce all sessions potentially involved in a data race need to use serializable; that can be easy or hard, depending on the scenario.

Re:Show HN: My experimental take on a decentralized ledger by jpgvm on Wednesday September 16, 2015 @10:28PM (#10231239)
Use UPSERT, it's correct -and- fast rather than just correct.

Increasing the transaction isolation level shouldn't be done out of laziness.