Transactions Controlling Concurrent Behavior Why Transactions Database systems

Transactions Controlling Concurrent Behavior

Why Transactions? • Database systems are normally being accessed by many users or processes at the same time. – Both queries and modifications. • Unlike operating systems, which support interaction of processes, a DMBS needs to keep processes from troublesome interactions.

ACID Transactions • ACID transactions are: – Atomic : Whole transaction or none is done. – Consistent : Database constraints preserved. – Isolated : It appears to the user as if only one process executes at a time. • That is, even though actions of several transactions might be interleaved, the net effect is identical to executing all transactions one after another in some serial order. – Durable : Effects of a process survive a crash. • Optional: weaker forms of transactions are often supported as well.

Transactions • A process that reads or modifies the DB is called a transaction. • It’s a unit of execution of database operations. Basic JDBC transaction pattern Connection conn =. . . ; conn. set. Auto. Commit(false); try {. . . //JDBC statements } finally { conn. commit(); }

Interleaving • For performance reasons, a DBMS has to interleave the actions of several transactions. However, the interleaving must be done carefully… • Consider two transactions T 1 and T 2, each of which, when running alone preserves database consistency: – T 1 transfers $100 from A to B, and – T 2 increments both A and B by 1% (e. g. daily interest) – Consider the following interleaving. (1) T 1 deducts $100 from A, (2) T 2 increments both A and B by 1%, (3) T 2 adds $100 to B. – What’s the problem? – B just lost $1.

COMMIT and ROLLBACK • The SQL statement COMMIT causes a transaction to complete. – It’s database modifications are now permanent in the database. • The SQL statement ROLLBACK also causes the transaction to end, but by aborting. – No effects on the database. • Failures like division by 0 or a constraint violation can also cause rollback, even if the programmer does not request it.

Transactions and Schedules • A transaction is a list of actions. The actions could be: – read, write, commit, abort • A schedule is a list of actions from a set of transactions. E. g. T 1 r(A) w(A) T 2 r(B) w(B) commit r(C) w(C) Commit

Anomalies: Reading Uncommitted Data T 1 r(A) w(A) T 2 r(A) w(A) r(B) w(B) commit • T 1 transfers $100 from A to B, and • T 2 increments both A and B by 1% (e. g. daily interest) • The problem is that the bank didn’t pay interest on the $100 that was being transferred. • Of course there would be no problem if we executed T 1 and after that T 2, or vice versa.

Anomalies: Unrepeatable Reads • Suppose that A is the number of copies available for a book. • Transactions T 1 and T 2 both place an order for this book. First they check the availability of the book. • Consider now the following: 1. T 1 checks whether A is greater than 1. Suppose T 1 sees (reads) value 1. 2. 3. 4. 5. • T 2 also reads A and sees 1. T 2 decrements A to 0. T 2 commits. T 1 tries to decrement A, which is now 0, and gets an error because some integrity check doesn’t allow it. This situation can never arise in a serial execution of T 1 and T 2.

Anomalies: Overwriting uncommitted data • • Suppose that Larry and Harry are two employees, and their salaries must be kept the equal. T 1 sets their salaries to $2000 and T 2 sets their salaries to $1000. Now consider the following schedule: T 1 r(Larry) w(Larry) T 2 r(Harry) w(Harry) r(Larry) w(Larry) commit Unfortunately, Harry will be paid more than Larry.

Summarizing the Terminology • A transaction (model) is a sequence of r and w actions on database elements. • A schedule is a sequence of reads/writes actions performed by a collection of transactions. – r. T(X) denotes T reads the DB element – w. T(X) denotes T writes X – If transactions are T 1, …, Tk, then we will simply use ri and wi, instead of r. Ti and w. Ti • Serial Schedule = All actions for each transaction are consecutive. r 1(A); w 1(A); r 1(B); w 1(B); r 2(A); w 2(A); r 2(B); w 2(B); … • Serializable Schedule: A schedule whose “effect” is equivalent to that of some serial schedule. • We will introduce a sufficient condition for serializability.

To flip or not to flip… • Suppose for DB elements X and Y, ri(X); rj(Y) is part of a schedule, and we flip the order of these operations. – ri(X); rj(Y) ≡ rj(Y); ri(X) – This holds always (even when X=Y) • We can flip ri(X); wj(Y), as long as X≠Y • That is, ri(X); wj (X) wj(X); ri (X) – In the RHS, Ti reads the value of X written by Tj, whereas it is not so in the LHS. • We can flip wi(X); wj(Y); provided X≠Y • However, wi(X); wj(X); wi(X); – The final value of X may be different depending on which write occurs last.

Conflicts • There is a conflict if one of two conditions hold. • A read and a write of the same X, or • Two writes of the same X • In such cases the operations may not be swapped in order. • All other events (reads/writes) may be swapped without changing the effect of the schedule (on the DB).

Precedence Graphs • If by swapping pairs of non conflicting actions in a schedule S, we end up in a serial schedule, then S is called a conflict serializable schedule. S: r 1(A); w 1(A); r 2(A); w 2(A); r 1(B); w 1(B); r 2(B); w 2(B); Serializability/precedence graph for S • Nodes: transactions {T 1, …, Tk} • Arcs: There is an arc from Ti to Tj if they have conflict access to the same database element X and Ti is first; • In written Ti <S Tj.

• If there is a cycle in the graph – Then, there is no serial schedule which is conflict equivalent to S. • Each arc represents a requirement on the order of transactions in a conflict equivalentserial schedule. • A cycle puts too many requirements on any linear order of transactions. • If there is no cycle in the graph – Then any topological order of the graph suggests a conflict equivalent schedule.

Why the Precedence Graph Test Works? Idea: if the precedence graph is acyclic, then we can swap actions to form a serial schedule. Proof: By induction on n, number of transactions. Basis: n = 1. That is, S={T 1}; then S is already serial. Induction: S={T 1, T 2, …, Tn}. Given that the precedence graph is acyclic, there exists Ti in S such that no Tj in S is dependent on. – We swap all actions of Ti to the front (of S). – (Actions of Ti)(Actions of the other n 1 transactions) – The tail is a precedence graph that is the same as the original without Ti, i. e. it has n 1 nodes. By the induction hypothesis, we can reorder the actions of the other transactions to turn it into a serial schedule

Schedulers • A scheduler takes requests from transactions for reads and writes, and decides if it is “OK” to allow them to operate on DB or defer them until it is safe to do so. • Ideal: a scheduler forwards a request iff it cannot lead to inconsistency of DB – Too hard to decide this in real time. • Real: it forwards a request if it cannot result in a violation of conflict serializability. • We thus need to develop schedulers which ensure conflict serializability.

Lock Actions • Before reading or writing an element X, a transaction Ti requests a lock on X from the scheduler. • The scheduler can either grant the lock to Ti or make Ti wait for the lock. • If granted, Ti should eventually unlock (release) the lock on X. • Shorthands: – li(X) = “transaction Ti requests a lock on X” – ui(X) = “Ti unlocks/releases the lock on X”

• The use of lock must be proper in 2 senses: – Consistency of Transactions: • Read or write X only when hold a lock on X. – ri(X) or wi(X) must be preceded by some li(X) with no intervening ui(X). • If Ti locks X, Ti must eventually unlock X. – Every li(X) must be followed by ui(X). – Legality of Schedules: • Two transactions may not have locked the same element X without one having first released the lock. – A schedule with li(X) cannot have another lj(X) until ui(X) appears in between

Legal Schedule Doesn’t Mean Serializable Consistency constraint required for this example: A=B

Two Phase Locking There is a simple condition, which guarantees conflict serializability: In every transaction, all lock requests (phase 1) precede all unlock requests (phase 2).

Why 2 PL Works? • Precisely: a legal schedule S of 2 PL transactions is conflict serializable. • Proof is an induction on n, the number of transactions. • Remember, conflicts involve only read/write actions, not locks, but the legality of the transaction requires that the r/w's be consistent with the l/u's.

Why 2 PL Works (Cont’d) • Basis: if n=1, then S={T 1}, and hence S is conflict serializable. • Induction: S={T 1, …, Tn}. Find the first transaction, say Ti, to perform an unlock action, say ui(X). We show that the r/w actions of Ti can be moved to the front of the other transactions without conflict. Consider some action such as wi(Y). Can it be preceded by some conflicting action wj(Y) or rj(Y)? In such a case we cannot swap them. • • – If so, then uj(Y) and li(Y) must intervene, as wj(Y). . . uj(Y). . . li(Y). . . wi(Y). – Since Ti is the first to unlock, ui(X) appears before uj(Y). – But then li(Y) appears after ui(X), contradicting 2 PL. • Conclusion: wi(Y) can slide forward in the schedule without conflict; similar argument for a ri(Y) action.

Shared/Exclusive Locks • Problem: while simple locks + 2 PL guarantee conflict serializability, they do not allow two readers of DB element X at the same time. • But having multiple readers is not a problem for conflict serializability (since read actions commute).

Shared/Exclusive Locks (Cont’d) • Solution: Two kinds of locks: 1. Shared lock sli(X) allows Ti to read, but not write X. – It prevents other transactions from writing X but not from reading X. 2. Exclusive lock xli(X) allows Ti to read and/or write X; no other transaction may read or write X.

• Consistency of transaction conditions: – A read ri(X) must be preceded by sli(X) or xli(X), with no intervening ui(X). – A write wi(X) must be preceded by xli(X), with no intervening ui(X). • Legal schedules: – No two exclusive locks. • If xli(X) appears in a schedule, then there cannot be a xlj(X) until after a ui(X) appears. – No exclusive and shared locks. • If xli(X) appears, there can be no slj(X) until after ui(X). • If sli(X) appears, there can be no wlj(X) until after ui(X). • 2 PL condition: – No transaction may have a sl(X) or xl(X) after a u(Y).

Scheduler Rules • When there is more than one kind of lock, the scheduler needs a rule that says “if there is already a lock of type A on DB element X, can I grant a lock of type B on X? ” • The compatibility matrix answers the question. Compatibility Matrix for Shared/Exclusive Locks is:

Upgrading Locks • Instead of taking an exclusive lock immediately, a transaction can take a shared lock on X, read X, and then upgrade the lock to exclusive so that it can write X. Upgrading Locks allows more concurrent operation: Had T 1 asked for an exclusive lock on B before reading B, the request would have been denied, because T 2 already has a shared lock on B.

Possibility for Deadlocks Example: T 1 and T 2 each reads X and later writes X. Problem: when we allow upgrades, it is easy to get into a deadlock situation.

Solution: Update Locks • • Update lock uli(X). – Only an update lock (not shared lock) can be upgraded to exclusive lock (if there are no shared locks anymore). – A transaction that will read and later on write some element A, asks initially for an update lock on A, and then asks for an exclusive lock on A. Such transaction doesn’t ask for a shared lock on A. Legal schedules: – read action permitted when there is either a shared or update lock. – An update lock can be granted while there is a shared lock, but the scheduler will not grant a shared lock when there is an update lock. – 2 PL condition: No transaction may have an sl(X), ul(X) or xl(X) after a u(Y).

Example T 1 sl(A); r(A) T 2 T 3 ul(A); r(A) sl(A) Denied xl(A) Denied u(A) xl(A); w(A) u(A) sl(A); r(A) u(A)

(No) Deadlock Example T 1 and T 2 each read X and later write X. Deadlock when using sl and xl locks only. Fine when using update locks.

What should we lock? • The whole table or just single rows? What’s database object? What should be the locking granularity? SELECT min(year) FROM Movies; • What happens if we insert a new tuple with the smallest year? • Phantom problem: A transaction retrieves a collection of tuples twice and sees different results, even though it doesn’t modify those tuples itself.

Transaction support in SQL • SET TRANSACTION ISOLATION LEVEL X – Where X can be • SERIALIZABLE (Default) • REPEATABLE READ • READ COMMITED • READ UNCOMMITED With a scheduler based on locks: • A SERIALIZABLE transaction obtains locks before reading and writing objects, including locks on sets (e. g. table) of objects that it requires to be unchangeable and holds them until the end, according to 2 PL. • A REPEATABLE READ transaction sets the same locks as a SERIALIZABLE transaction, except that it doesn’t lock sets of objects, but only individual objects.

Transaction support in SQL • • A READ COMMITED transaction T obtains exclusive locks before writing objects and keeps them until the end. However, it obtains shared locks before reading values and then immediately releases them; their effect is to ensure that the transaction that last modified the values is complete. Thus, 1. T reads only the changes made by committed transactions. 2. No value written by T is changed by any other transaction until T is completed. 3. However, a value read by T may well be modified by another transaction (which eventually commits) while T is still in progress. 4. T is also exposed to the phantom problem. A READ UNCOMMITED transaction doesn’t obtain any shared lock at all. So, it can read data that is being modified. Such transactions are allowed to be READ ONLY only. So, such transaction doesn’t ask for any lock at all.

In Summary Level Reading Uncommited Data (Dirty Read) Unrepeatable Read Phantom READ UNCOMMITED Maybe READ COMMITTED No Maybe REPEATABLE READ No No Maybe SERIALIZABLE No No No