Conflict + View + Concurrency

Rahul Jain25 asked Oct 22, 2016 • retagged Jun 4, 2017 by Arjun

583 views

1 votes

Do they all ensure serializability???

Strict 2PL

Rigirous 2PL

Conservative 2PL

Multiversion 2PL

Timestamp

Stirct timestamp

Multiversion timestamp

Graph based protocol

Thomas write rule

Multiple granuality

And among them which policy allows schedules that are not conflict serializable by are view serializable???

Databases
view-serializable
conflict-serializable
transaction-and-concurrency
databases
concurrency

+ –

Rahul Jain25 asked Oct 22, 2016 • retagged Jun 4, 2017 by Arjun

Rahul Jain25

583 views

See all

0 Please log in or register to add a comment.

Please log in or register to answer this question.

1 Answer

1 votes

Strict 2PL

Rigirous 2PL

Conservative 2PL

Multiversion 2PL

Timestamp

Stirct timestamp

Multiversion timestamp

Graph based protocol

These ensure conflict serializibility

Thomas write rule doesn't

Ashwin Kulkarni answered Nov 16, 2017

Ashwin Kulkarni

See all

0 Please log in or register to add a comment.

Voting & Accepting an answer helps improve the community

← Previous Next →

← Previous in category Next in category →

Related questions

2 votes

1 answer

Parshu gate asked Dec 5, 2017

943 views

Conflict and View serializable

Parshu gate

943 views

Parshu gate asked Dec 5, 2017

Databases
conflict-serializable
view-serializable
transaction-and-concurrency
databases
concurrency

+ –

11 votes

2 answers

vix28 asked Sep 8, 2016

12,222 views

serializablity and recoverability of schedules
1) T1: R(X), T2: W(X), T1: W(X), T2: Abort, T1: Commit 2) T1: W(X), T2: R(X), T1: W(X), T2: Abort, T1: Commit 3) T1: W(X), T2: R(X), T1: W(X), T2: ... : Abort Can anyone explain whether these schedules are serializable, conflict-serializable, view serializable, recoverable, avoids-cascading-aborts, and strict? The abort operation actually bugging me.

1) T1: R(X), T2: W(X), T1: W(X), T2: Abort, T1: Commit2) T1: W(X), T2: R(X), T1: W(X), T2: Abort, T1: Commit3) T1: W(X), T2: R(X), T1: W(X), T2: Commit, T1: AbortCan anyo...

vix28

12.2k views

vix28 asked Sep 8, 2016

Databases
transaction-and-concurrency
concurrency
conflict-serializable
view-serializable
databases

+ –

9 votes

1 answer

flow2539 asked May 28, 2018

3,519 views

Are aborted transactions ALWAYS ignored when determining result/view/conflict serializability?
I am looking for some clarity on this topic. Here is some random schedule as an example: $r1(x) w1(x) r2(x) w2(x) r3(y) r3(x) w3(x) c3 a1 c2$ I was told, that for ... , strictness or avoidance of cascading rollbacks. I would be grateful if the question would be answered since this really confuses me.

I am looking for some clarity on this topic. Here is some random schedule as an example:$r1(x) w1(x) r2(x) w2(x) r3(y) r3(x) w3(x) c3 a1 c2$I was told, that for conflict...

flow2539

3.5k views

flow2539 asked May 28, 2018

Databases
databases
transaction-and-concurrency
conflict-serializable
view-serializable
result-serializable
serializability

+ –

3 votes

3 answers

shivangi5 asked Dec 6, 2017

2,970 views

VIEW SERIALIZABILITY
Consider the 2 transactions T1: R(A) W(A) W(B) T2: R(A) W(A) R(B) W(B) How many view serializable schedules are possible which are not conflict serializable? (A) 0 (B) 1 (C) 2 (D) 3

Consider the 2 transactionsT1: R(A) W(A) W(B)T2: R(A) W(A) R(B) W(B)How many view serializable schedules are possible which are not conflict serializable?(A) 0(B) 1(C) 2(...

shivangi5

3.0k views