康辉《数据库系统概念》教学课件9.pptVIP

Chapter 16: Concurrency Control 16.1 Lock-Based Protocols 16.1 Lock-Based Protocols 16.1 Lock-Based Protocols Pitfalls of Lock-Based Protocols Pitfalls of Lock-Based Protocols Locking Protocol A locking protocol (封锁协议) is a set of rules followed by all transactions while requesting and releasing locks. Locking protocols restrict the set of possible schedules. We say that a schedule S is legal under a given locking protocol if S is a possible schedule for a set of transactions that follow the rules of the locking protocol We say that a locking protocol ensures conflict serializability if and only if all legal schedules are conflict serializable 16.1.3 The Two-Phase Locking Protocol 16.1.3 The Two-Phase Locking Protocol 16.1.3 The Two-Phase Locking Protocol 长锁：保持到事务结束时才释放的锁； 短锁：在事务中途就可以释放的锁。 Lock Conversions 16.1.3 The Two-Phase Locking Protocol Automatic Acquisition of Locks Automatic Acquisition of Locks Implementation of Locking A lock manager can be implemented as a separate process to which transactions send lock and unlock requests The lock manager replies to a lock request by sending a lock grant messages (or a message asking the transaction to roll back, in case of a deadlock) The requesting transaction waits until its request is answered The lock manager maintains a data-structure called a lock table to record granted locks and pending requests 锁表通常实现为以被锁数据项的名字为索引的内存散列表 Lock Table Black rectangles indicate granted locks, white ones indicate waiting requests Lock table also records the type of lock granted or requested New request is added to the end of the queue of requests for the data item, and granted if it is compatible with all earlier locks Unlock requests result in the request being deleted, and later requests are checked to see if they can now be granted If transaction aborts, all waiting or granted requests of the transaction are deleted lock manager may keep a list of locks held by each transaction, to implement this efficiently 16.1.5 G