TPS

Concurrent Execution
KALINGA INSTITUTE OF INDUSTRIAL
TECHNOLOGY

School Of Computer
Engineering

Dr. Amiya Ranjan Panda

Assistant Professor [II]
School of Computer Engineering,
Kalinga Institute of Industrial Technology (KIIT),
Deemed to be University,Odisha

4 Credit Lecture Note 2

Chapter Contents
2

 Concurrent Execution
 Schedules
 Serial Schedule
 Concurrent Schedule

 Equivalent Schedule
 Result Equivalent Schedule
 Conflict Equivalent Schedule

 Serializability
 Conflict Serializability
 Testing for Conflict Serializability
 View Serializability
Concurrent Execution
3
 Concurrent execution of transactions means executing more than one
transaction at the same time.
 In the serial execution, one transaction can start executing only after the
completion of the previous.
 The advantages of using concurrent execution of transactions are:
 Improved throughput and resource utilization.
 Reduced waiting time.
 The database system must control the interaction among the concurrent
transactions to prevent them from destroying the consistency of the database. It
does this through a variety of mechanisms called concurrency control schemes.

 T1 transfers $100 from account A to account B

 T2 transfers 20% of balance from account A to account B
Schedule & Serial Schedule
4
 Concurrent execution of transactions means executing more than one
transaction at the same time.
 A schedule is a sequence that indicates the chronological order in which
instructions of concurrent transactions are executed.
 A schedule for a set of transactions must consist of all instructions of those
transactions.
 We must preserve the order in which the instructions appear in each individual
transaction.
 Serial Schedule:
 A serial schedule is a schedule where all the instructions belonging to each
transaction appear together.
 There is no interleaving of transaction operations. A serial schedule has no
concurrency and therefore it does not interleave the actions of different
transactions.
 For n transactions, there are exactly n! different serial schedules possible.
Serial Schedule…
5

T1 T2 T1 T2
Read(A); Read(A);
A:=A-100; Temp=0.2*A;
Write(A); A:=A-Temp;
Read(B); Write(A);
B:=B+100; Read(B);
Write(B); B:=B+Temp;
Read(A); Write(B);
Temp=0.2*A; Read(A);
A:=A-Temp; A:=A-100;
Write(A); Write(A);
Read(B); Read(B);
B:=B+Temp; B:=B+100;
Write(B); Write(B);

Schedule1 Schedule2
(T1 followed by T2) (T2 followed by T1)
Concurrent Schedule
6
 In concurrent schedule, operations from different concurrent transactions are
interleaved.
 The number of possible schedules for a set of n transactions is much larger than
n!.
T1 T2 T1 T2 T1 T2
Read(A); Read(A); Read(A);
A:=A-100; A:=A-100; A:=A-100;
Write(A); Read(A); Write(A);
Read(A); Temp=0.2*A; Read(A);
Temp=0.2*A; A:=A-Temp; Temp=0.2*A;
A:=A-Temp; Write(A); A:=A-Temp;
Write(A); Read(B); Read(B);
Read(B); Write(A); B:=B+100;
B:=B+100; Read(B); Write(A);
Write(B); B:=B+100; Read(B);
Read(B); Write(B); B:=B+Temp;
B:=B+Temp; B:=B+Temp; Write(B);
Write(B); Write(B); Write(B);
Schedule 3 Schedule 4 Schedule 5
Equivalent Schedule
7
 Equivalent Schedule: Two schedules S1 and S2 are said to be equivalent
schedules, if they produce the same database state.
 Result Equivalent Schedule: Two schedules are said to be result equivalent if
they produce the same final database state for some initial value of data.
 Conflict Equivalent Schedule: Two schedules are said to be conflict
equivalent if all the conflicting operations in both the schedules must be
executed in the same order.
 The conflicting operations are read-write, write-read and write-write
(different transaction, same data item, at least one write).

Ti Tj
Read(A) Write (A)
Write (A) Read (A)
Write (A) Write (A)
Read(A) Read(A)
Result Equivalent Schedule Example
8
 The following schedules are result equivalent for the initial value of X and Y
( 2 and 5) respectively on not.

S1 S2
T1 T2 T1 T2
Read(X); Read(X);
X:=X+5; X=X * 3;
Write(X); Write(X);
Read(X); Read(X);
X=X * 3; X:=X+5;
Write(X); Write(X);
Read(Y);
Read(Y); Y:=Y+5;
Y:=Y+5; Write(Y);
Write(Y);
Conflict Equivalent Schedule Example
9
 Check whether following schedules are conflict equivalent.
S1 S2
1. T1 T2 T1 T2
Read (X) Read (X)
Write(X) Write(X)
Read (X) Read(X)
Write(X) Read(Y)
Read (Y) Write (X)
Write (Y) Write(Y)
2.
S1: R1(A), R2(B), W1(A), W2(B)
S2: R2(B), R1(A), W2(B), W1(A)

3. S1: R1(A), W1(A), R2(B), W2(B), R1(B)

S2: R1(A), W1(A), R1(B), R2(B), W2(B)

4. S1: R2(A), R1(A), W2(B), W1(B)

S2: R1(A), R2(A), W2(B), W1(B)
Serializability
10
 A concurrent schedule is serializable if it is equivalent to a serial schedule.
 Serial schedules preserve consistency as we assume each transaction
individually preserves consistency.
 The database system must control concurrent execution of transactions to
ensure that the database state remains consistent.
 Since the modifications are done in the local buffer, we can ignore the
operations other than Read and Write instructions for easier understanding of
the serializability.
Serializability
11
S1 S2
T1 T2 T1 T2
Read(A); Read(A);
Write(A); Write(A);
Read(B); Read(B);
Write(B); Write(B);
Read(A); Read(A);
Write(A); Write(A);
Read(B); Read(B);
Write(B); Write(B);
S3 S4 S5
T1 T2 T1 T2 T1 T2
Read(A); Read(A); Read(A);
Write(A); Read(A); Write(A);
Read(A); Write(A); Read(A);
Write(A); Read(B); Read(B);
Read(B); Write(A); Write(A);
Write(B); Read(B); Read(B);
Read(B); Write(B); Write(B);
Write(B); Write(B); Write(B);
Conflict Serializability
12
 A concurrent schedule is serializable if it is equivalent to a serial schedule.
 Conflict Serializability consists of conflicting operations. Let us consider a
schedule S in which there are two consecutive instructions, Ii and Ij of
transactions Ti and Tj respectively.
 If Ii and Ij access different data items, then we can swap Ii and Ij without
affecting the results of any transactions in the schedule. However, if Ii and Ij
access the same data item Q, then the order of the two instructions may matter:
 Case-1: Ii =Read(Q) and Ij =Read(Q):
 Order of Ii and Ij does not matter
 Case-2: Ii =Read(Q) and Ij =Write(Q):
 Order of Ii and Ij matters in a schedule
 Case-3: Ii =Write(Q) and Ij =Read(Q):
 Order of Ii and Ij matters in a schedule
 Case-1: Ii =Write(Q) and Ij =Write(Q):
 Order of Ii and Ij matters in a schedule
Conflict Serializability…
13
 A concurrent schedule is serializable if it is equivalent to a serial schedule.
 Thus, Ii and Ij conflict if they are the instructions by different transactions on
the same data item, and at least one of these instructions is a write operation.
 Let Ii and Ij be consecutive instructions of a schedule S. If Ii and Ij are
instructions of different transactions and they do not conflict, then we can swap
the order of Ii and Ij to produce a new schedule S’. Here, we expect S to be
equivalent to S’.
 If a schedule S can be transformed into a schedule S’ by a series of swaps of
non-conflicting instructions, we say that S and S’ are conflict equivalent.
 A concurrent schedule S is conflict serializable if it is conflict equivalent to
a serial schedule.
Conflict Serializability…
14
 Whether S6 and S7 are conflict serializable or nor ?
S6 S8
1. T1 T2 T1 T2
Read(X); Read(X);
Write(X); Write(X);
Read(X); Read(Y);
Write(X); Write(Y);
Read(Y); Read(X);
Write(Y); Write(X);
Read(Y);
Read(Y);
Write(Y);
Write(Y);
2. S7
T1 T2 S9
T1 T2
Read(X);
Write(X); Read(X);
Read(X);
Write(X);
Write(X); Read(Y);
Read(Y); Write(Y);
Write(Y); Read(X);
Read(Y); Write(X);
Write(Y); Read(Y);
Write(Y);
Testing for Conflict Serializability
15
 Construct a directed graph, called a precedence graph from S. This graph
consists of a pair G = (V, E), where V is a set of vertices and E is a set of edges.
 The set of vertices consists of all the transactions participating in the schedule.
 The set of edges consists of all edges Ti → Tj for which one of three
conditions holds:
 Ti executes write(Q) before Tj executes read(Q)
 Ti executes read(Q) before Tj executes write(Q)
 Ti executes write(Q) before Tj executes write(Q)
 If an edge Ti → Tj exists in the precedence graph, then in any serial schedule
S’ equivalent to S, Ti must appear before Tj.
 If the precedence graph for a concurrent schedule S has a cycle, then that
schedule is not conflict serializable. If the graph contains no cycles, then
the schedule S is conflict serializable.
Testing for Conflict Serializability
16
View Serializability
17
 A schedule S is view serializable, if it is view equivalent to a serial
schedule.
 View Equivalence: Two schedules are view equivalence if and only if for
every read operation, the source should be same in both the schedule.
Assume an initial transaction T0, which writes every data item and a final
transaction Tf, which reads every data item.
 View Serializable Schedule: A schedule is said to be view serializable
schedule if and only if it is view equivalent to any of its serial schedule.
 A schedule that is not conflict serializable but view serializable, must
always contain atleast one blind write operation.
 If a schedule doesn’t contain any blind write operation, both conflict
serializable and view serializable conditions are same.
View Serializability
18
 The schedules S and S1 are said to be view equivalent if the following
three conditions are met:
 For each data item Q, if transaction Ti reads the initial value of Q in
schedule S, then it must also read the initial value of Q in schedule S1.
 For each data item Q, the transaction that performs the final Write(Q)
operation in schedule S must also perform the final Write(Q) operation
in schedule S1.
 For each data item Q, if transaction Ti executes Read(Q) in schedule S,
and if that value was produced by a Write(Q) operation executed by
transaction Tj ; then in schedule S1, the Read(Q) operation of Ti must
also read the value of Q that was produced by the same Write(Q)
operation of transaction Tj.
 A schedule S is view serializable if it is view equivalent to a serial
schedule.
View Serializability
19

T1 T2 T3 T1 T2 T3
Read(Q); Read(Q);
Write(Q); Write(Q);
Write(Q);
Write(Q);
Write(Q); Write(Q);
Schedule 7 Schedule 8

 This schedule is view serializable.

 This schedule is not conflict serializable.
 Every conflict serializable schedule is also view serializable, whereas all
view serializable schedules are not conflict serializable.
 Every view serializable schedule, which is not conflict serializable, has
blind writes.
View Serializability
20
Conflict
Serializable
& View
No Cycle Serializable
Conflict
Serializable
Schedule Condition:
Precedence Cycle
Graph
At-least No Not View
one Blind
Serializable
Write

Yes Cycle
View
Serializable
Condition: No Cycle
Poly Graph View
Serializable
21