PROTOCOLS(基于锁的协议).ppt

Chapter 16: Concurrency Control Lock-Based Protocols（基于锁的协议） Lock-Based Protocols (Cont.) Lock-Based Protocols (Cont.) Lock-Based Protocols (Cont.) Pitfalls of Lock-Based Protocols Pitfalls of Lock-Based Protocols (Cont.) The Two-Phase Locking Protocol（两段锁协议） The Two-Phase Locking Protocol (Cont.) The Two-Phase Locking Protocol (Cont.) Lock Conversions（锁的转换） Lock Conversions（锁的转换） Graph-Based Protocols（基于图的协议） Tree Protocol（树形协议） Tree Protocol Tree Protocol(Cont.) Timestamp-Based Protocols (基于时间戳的协议) Timestamp-Based Protocols (Cont.) Timestamp-Based Protocols (Cont.) Example Use of the Protocol Example Use of the Protocol Thomas’ Write Rule（托马斯写规则） Validation-Based Protocol （基于有效性检查的协议） Validation-Based Protocol (Cont.) Schedule Produced by Validation Multiple Granularity （多粒度） Example of Granularity Hierarchy Multiversion Schemes （多版本机制） Deadlock Handling （死锁处理） Deadlock Handling More Deadlock Prevention Strategies Deadlock prevention (Cont.) Deadlock Detection Deadlock Detection (Cont.) Deadlock Recovery Insert and Delete Operations Insert and Delete Operations (Cont.) Index Locking Protocol Weak Levels of Consistency Degree-two consistency: differs from two-phase locking in that S-locks may be released at any time, and locks may be acquired at any time X-locks must be held till end of transaction Serializability is not guaranteed, programmer must ensure that no erroneous database state will occur] Cursor stability: For reads, each tuple is locked, read, and lock is immediately released X-locks are held till end of transaction Special case of degree-two consistency Weak Levels of Consistency in SQL SQL allows non-serializable executions Serializable: is the default Repeatable read: allows only committed records to be read, and repeating a read should return the same value (so read locks should be retained) However, the phantom phenomenon need not be prevented T1 may see some records inserted by T2, but may not see others inserted by T2 Read committed: same as