<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High-Performance Concurrency Control Mechanisms for Main-Memory Databases · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1201.0228/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1201.0228/feed.xml" rel="self" type="application/rss+xml" /><item><title>High-Performance Concurrency Control Mechanisms for Main-Memory Databases — mentioned by tintor</title><link>https://news.ycombinator.com/item?id=4165412</link><guid isPermaLink="false">urn:hackerpapers:mention:1201.0228:4165412</guid><pubDate>Wed, 27 Jun 2012 03:51:44 GMT</pubDate><description>&lt;p&gt;@Criss Isolation levels are used to specify semantics only. DBMS is free to implement them in different ways. Take a look at this VLDB 2012 paper about optimistic concurrent control in main memory databases, like MemSQL, which also describes implementation of isolation levels: http://arxiv.org/pdf/1201.0228v1.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1201.0228/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item></channel></rss>
