Home › GATE CSE › computerscience › Database Management Systems › Two schedules are conflict equivalent when
Two schedules are conflict equivalent when
Athey commit the same number of transactions
Byou can swap consecutive non-conflicting ops
Cthey have identical wall-clock execution times
Dthey use the same locking protocol
Answer & Solution
Correct answer: B. you can swap consecutive non-conflicting ops
Conflict equivalence is a syntactic equivalence: it allows swapping consecutive operations only when they do not conflict (different items, or same-item reads). Swapping conflicting ops would change the semantics. Commit counts, timing and locking choices are unrelated.
Related questions
The main reasons production DBMSs avoid shadow paging in favour of WAL are that shadow pagWhat is the purpose of a Compensation Log Record (CLR) in ARIES?ARIES recovery is structured as exactlyFuzzy checkpoints differ from naive checkpoints byIn standard log-based recovery, the order of operations isAfter a crash, with checkpointing, the recovery system scans the logA complete log record for a write operation includesPer WAL semantics, a transaction is officially committed at the moment