• edited by
3,279 views

4 Answers

Best answer
4 4 votes
Any schedule produced by basic time based protocol is confluct-serialuzable (there is an equivalent serial schedule which is conflict equivalent).

Same is the case for 2PL scheme. Any schedule produced by 2PL scheme is conflict serializable.

Now coming to the actual question -- answer is no. Infact 2PL and time stamp based approach both produces a strict subset of all possible conflict serializable schedules. Also not all schedules produced by 2PL can be produced by a timestamp based approach or vice versa.
• selected by
1 1 vote

suppose, TS(T1)=10 & TS(T2)=20, then following schedule is conflict serializable.

T1 T2
  W(Q)
R(Q)  

but, this is not possible under timestamp because it violets T1-->T2 

0 0 votes
as pointed out by @miniR, it is not necessary.

Timestamp ordering protocol requires the schedule to be conflict serializable in the order of the increasing timestamps. For example,

Let TS(T1) = 10, TS(T2) = 20; If the schedule turns out to be conflict serializable in the order T2->T1, it still does not get accepted in the timestamp protocol, and T1 gets aborted and re-enters the system with a new timestamp.
• edited by
Position:
Show:

Related questions

3 3 votes
1 1 answer
2.1k
2.1k views
1 1 vote
1 1 answer
1.4k
1.4k views
Harsh Saini_1 asked Dec 27, 2023
1,443 views
How many total $Conflict$ $Serializable$ $Schedules$ are possible that can be formed by $T1$ and $T2?$$T1:$ $r_1(A)$ $r_1(B)$ $w_1(B)$$T2:$ $r_2(B)$ $r_2(A)$ $w_2(B)$
2 2 votes
1 1 answer
1.1k
1.1k views
KISHALAY DAS asked Dec 22, 2016
1,139 views
State which of the protocols allows the schedule\[\begin{array}{l}T_{1}: R(x), T_{2}: W(x), T_{1}: W(x), T_{3}: R(x), \\T_{1}: \text { commit, } T_{2}: \text { commit, } ...
2 2 votes
1 answers 1 answer
3.9k
3.9k views
Rahul Jain25 asked Feb 4, 2017
3,936 views
I)All schedules that are allowed under 2PL are also allowed under Timestamp?? Is vice versa true??II)Plz explain by giving example. I have read that there are schedules t...