1 / 5

CS 775/875: Fall 2000

CS 775/875: Fall 2000. Chapter 12: Transactions and Concurrency Control. Transactions. What is a transaction? ACID properties: Atomicity, Consistency, Isolation, Durability Serializable transactions Open, close, commit/abort

callia
Télécharger la présentation

CS 775/875: Fall 2000

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CS 775/875: Fall 2000 Chapter 12: Transactions and Concurrency Control

  2. Transactions • What is a transaction? • ACID properties: Atomicity, Consistency, Isolation, Durability • Serializable transactions • Open, close, commit/abort • Concurrency control---The lost update problem, inconsistent retrieval, serial equivalence • Conflicting Operations • Dirty reads, premature writes, cascaded aborts, tentative versions • Nested Transactions • Locks; implementation; nested transactions • Deadlocks

  3. Optimistic Concurrency Control • Locks present an overhead, may cause deadlocks, reduces concurrency • Optimistic---assumes that data conflicts are rare • Kung and Robinson algorithm: Working phase, validation phase, update phase • Tentative versions, reads on committed versions only, writes on tentative versions • Validation of transactions: Backward validation and forward validation; transaction numbers assigned at the beginning of validation phase; • Only one transaction can be in the validation phase; until this is completed, no new validation begins

  4. Optimistic Concurrency Control • See Fig. 12.28 http://www.cdk3.net/ig/slides/Chapter12Slides.pdf • Backward validation: Compare readset with the already committed transactions • Forward validation: Compare writeset with the readsets of all overlapping active transactions • Starvation is a problem with optimistic CC

  5. Timestamp Ordering • Basic TO rule: “A transaction’s request to write an object is valid only if that object was last read and written by earlier transactions. A transaction’s request to read an object is valid only if that object was last written by an earlier transaction. • Transactions are only committed in the order of their numbers. • See Fig. 12.30 and 12.31 • http://www.cdk3.net/ig/slides/Chapter12Slides.pdf • Multiversion TS ordering

More Related