Home › GATE CSE › computerscience › Database Management Systems › If a DBMS using detection-then-abort keeps selec…
If a DBMS using detection-then-abort keeps selecting the same transaction as victim, the problem that arises is
Adeadlocks become unbounded in number
Bstarvation: same transaction aborted repeatedly
Cthe wait-for graph stops being directed
Dlock compatibility breaks down
Answer & Solution
Correct answer: B. starvation: same transaction aborted repeatedly
Starvation: that transaction never completes because every cycle gets resolved by aborting it. DBMSs track victim counts and rotate victim selection to give starving transactions a turn. Deadlock count, graph direction, and compatibility are not affected by victim selection.
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