Database management system with efficient version control
First Claim
1. A method for processing data, comprising:
- creating a pending content item from a committed content item for a first transaction;
providing a second transaction read access to the committed content item while providing the first transaction read/write access to the pending content item;
flagging the committed content item as deleted when the first transaction commits the pending content item; and
deferring deallocation of the committed content item until the second transaction finishes accessing the committed content item.
5 Assignments
0 Petitions
Accused Products
Abstract
A two copy versioning scheme is proposed. The scheme provides efficient implementation for a high read load database and eliminates read dependencies. The versioning scheme provides efficient implementation for transactions executing under ANSI READ COMMITTED isolation, and is extensible to serializable isolation. The two-copy versioning scheme is garbage free meaning that all versions of data records are used during execution and is adapted to index scanning operations. A “deferred delete” scheme allows read transactions to complete data deallocation operations. Statements that require “snapshots” are efficiently supported.
-
Citations
17 Claims
-
1. A method for processing data, comprising:
-
creating a pending content item from a committed content item for a first transaction;
providing a second transaction read access to the committed content item while providing the first transaction read/write access to the pending content item;
flagging the committed content item as deleted when the first transaction commits the pending content item; and
deferring deallocation of the committed content item until the second transaction finishes accessing the committed content item. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A database system, comprising:
-
a database containing physical content items; and
a processor creating a pending content item from a committed content item for a write transaction and providing a read transaction access to the committed content item while providing the write transaction access to the pending content item, the processor flagging the committed content item as deleted when the write transaction commits the pending content item and deferring deallocation of the committed content item until the read transaction finishes accessing the committed content item. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17)
-
Specification