操作失误 文档没保存。。。只剩下这些了
Serializable Snapshot Isolation in PostgreSQL
This paper describes our experience implementing PostgreSQL’s new serializable isolation level. It is based on the recently-developed Serializable Snapshot Isolation (SSI) technique.
how snapshot isolation differs from serializability and why we view serializability as an important DBMS feature in Section
In snapshot isolation, all reads within a transaction see a consistent view of the database, as though the transaction operates on a private snapshot of the database taken before its first read. SI prohibits concurrent transactions from modifying the same data.
providing serializability in the database is an important simplification for application developers, because concurrency issues are notoriously difficult to deal with.
SERIALIZABLESNAPSHOTISOLATION
Snapshot Isolation Anomalies
SI allowed non-serializable executions but did not exhibit any of the well-understood anomalies proscribed by the SQL standard [5], This suggested that existing isolation level definitions were inadequate, and prompted an effort to define the anomalies caused by SI and when they arise.
救命啊,好难
这个文章好多东西不懂,是代码实现层面的。
MULTIVERSION REPEATABLE READ ISOLATION LEVEL – THEORY AND PRACTICE
这篇文章浅显易懂,他最大的帮助是帮我找到了经典的MVCC论文。
这篇文献没有人引用,我感觉是和本科毕设同水平的垃圾论文,我把毕设好好弄也能发表(bushi)
但是我不知道其为何垃圾。这个文献提出了一种新的snapshot算法,这个算法于以往的不同是,每次进行写的时候,需要重新去读数据的最新版本(latest version)。这样的好处是,防止了一些X+Y 的问题。(我都有点懵了 什么时候能发生race condition, 什么时候不能啊?)
但是他又没说代码实现的细节,没说测试的细节,所以很垃圾吧。
Concurrency control in distributed database systems
The heart of our analysts is a decomposition of the concurrency control problem into two major subproblems: read-write and write-write synchronization.

文章讨论了PostgreSQL在实现可序列化隔离级别的过程中遇到的挑战和经验,指出可序列化对于DBMS的重要性,因为它简化了应用开发者处理并发问题的复杂性。文中提及SnapshotIsolation的异常情况,并对比了Multi-VersionRepeatableRead隔离级别,特别是提出的一种新算法,该算法在写操作时获取最新数据版本以避免某些并发问题,但未详细说明实现和测试细节。

624

被折叠的 条评论
为什么被折叠?



