Conflicts are the reason for blocking transactions and delays ( non-materialized conflicts ), or for aborting transactions due to serializability violations prevention.
42.
Only executed ( " materialized " ) conflicting operations are relevant to " conflict serializability " ( see more below ).
43.
No other interesting generalizing variants ( which guarantee global serializability with no local concurrency control information distribution ) are known, but may be discovered.
44.
This partially explains the popularity of SS2PL as a solution ( practically, the only solution, for many years ) for achieving global serializability.
45.
Classes of schedules defined by " relaxed global serializability " properties either contain the global serializability class, or are incomparable with it.
46.
Classes of schedules defined by " relaxed global serializability " properties either contain the global serializability class, or are incomparable with it.
47.
It seems that they have not understood the article and what is so special in Commitment ordering ( see it explicitly in Global serializability ).
48.
This book neither mentions CO nor references it, and strangely, apparently does not consider CO a valid " Global serializability " solution.
49.
Improper synchronization can lead to multiple failure modes including loss of atomicity, consistency, isolation and durability, deadlock, livelock and loss of serializability.
50.
No serialization failure is possible in this mode ( because no promise of serializability is made ), and Transaction 1 will not have to be retried.