User:Comps

(Account information: block log · CentralAuth · suspected sockpuppets · confirmed sockpuppets · sock…

User:Comps
Committed identity: 00577c4134d7fcb538565824664a9a2300034fc23efdd299accc7991f02572c049116988ea16a23a15264840cf2643b65227c5041c1715daebc0b29790889c6c is an SHA-512 commitment to this user's real-life identity.

Contributions to Wikipedia since March 2006:

Major articles I have written

(unfortunately with no others' contributions to structure and content; others' edit and language contributions are appreciated)

Serializability

New term introduced for clarity:
Materialized conflict
A regular conflict graph has an edge for every materialized conflict; a regular wait-for graph has an edge for every non-materialized conflict (typically due to blocking by a lock). According to the common conventions directions of edges represent in the two graphs types opposite time orders between conflicting operations. The new term allows a unified treatment for both materialized and non-materialized conflicts, which simplifies the discussion about Commitment ordering (CO; see below).

Global serializability

Commitment ordering (CO)

New terms introduced for clarity and simplicity of presentation:
Voting deadlock
A voting deadlock in the atomic commitment protocol. In the original CO papers these deadlocks are discussed and referred to only as "deadlocks." The new name better describes them for the respective discussions and separates them from other deadlock types.
Augmented conflict graph
This graph has an edge for every conflict, either materialized or non materialized, and it is the union of the (regular) conflict graph with the (reversed edge, regular) wait-for graph. In the presence of CO this graph is a (reversed edge) wait-for graph for voting, and has a global cycle iff a voting deadlock exists. This graph allows a more compact description of the conditions for voting deadlocks, which are an essential element in the operation of the distributed CO algorithm.

The History of Commitment Ordering

Two-phase locking

Major article rewrite and revision

Concurrency control in databases section in Concurrency control - Almost a complete rewrite and major expansion. An expanded lead section to the containing article.

Database - Major reorganization, rewrite, expansion, and multiple section addition. A revised and expanded lead section. Since 6 May, 2011

Two-phase commit protocol - Major rewrite and expansion of lead section. A new section: Implementing the two-phase commit protocol.

Schedule (computer science) - Major reorganization, lead section revision, and new opening section: Describing a schedule formally.

Index locking - A complete rewrite.

Database management system - Major revision of lead section (12 May, 2011)

Other major contributions

in these articles:

Distributed concurrency control

Global concurrency control

Snapshot isolation

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.