Database system with transaction control block index

Patent metadata

Field	Value
Publication number	US-9824134-B2
Application number	US-201414553494-A
Country	US
Kind code	B2
Filing date	Nov 25, 2014
Priority date	Nov 25, 2014
Publication date	Nov 21, 2017
Grant date	Nov 21, 2017

Abstract

A plurality of transactions is handled in a database. Each transaction includes a plurality of operations on at least one record in the database with at least two of the transactions being handled concurrently. Thereafter, a temporary timestamp is assigned to each record. The temporary timestamp are based, at least in part, on the corresponding transaction. Further, a final timestamp is assigned to each record with a commit operation. It can later be determined, using a visibility function and based on the assigned temporary timestamps and final timestamps, which of the records are visible in a consistent view for a first transaction. Based on such determination, access can be provided to those records determined to be visible to be accessed to the first transaction.

First claim

What is claimed is:

1. A method for implementation by one or more hardware data processors forming part of at least one computing device, the method comprising:
handling a first transaction in a database, the first transaction comprising a plurality of operations on at least a first record in the database, and the first transaction being handled concurrently with at least a second transaction;
assigning, to the first record, a first timestamp, the first timestamp being a temporary timestamp corresponding to the first transaction, the first timestamp being converted from the temporary timestamp to a final timestamp by at least performing a commit operation with respect to the first transaction, and the converting from the temporary timestamp to the final timestamp comprising:
entering a commit lock;
determining a commit timestamp by at least increasing, by a first increment, the value of the commit timestamp generator;
issuing a write memory barrier;
setting, based at least on the commit timestamp, the final timestamp for the first record;
increasing, by a second increment, the value of the commit timestamp generator value; and
releasing the commit lock; and

determining that the first record is available as part of a consistent view for the second transaction, the determining being based at least on a second timestamp of the consistent view being higher than the first timestamp of the first record; and
in response to determining that the first record is available as part of the consistent view for the second transaction, including the first record in the consistent view for the second transaction, the inclusion of the first record in the consistent view enabling the first record to be accessed by the second transaction.

2. The method of claim 1 , wherein the first transaction and/or the second transaction are associated with a corresponding transaction control block index that is specific to each transaction.

3. The method of claim 1 , wherein the final timestamp corresponds to a value of a commit timestamp generator.

4. The method of claim 3 , further comprising:
selectively locking the commit timestamp generator to at least prevent the commit timestamp generator from issuing additional timestamps.

5. The method of claim 1 , wherein the database comprises an in-memory database.

6. The method of claim 5 , wherein the in-memory database is an in-memory columnar database storing data in columns.

7. A non-transitory computer program product storing instructions which, when executed by at least one hardware data processor forming part of at least one computing device, result in operations comprising:
handling a first transaction in a database, the first transaction comprising a plurality of operations on at least a first record in the database, and the first transaction being handled concurrently with at least a second transaction;
assigning, to the first record, a first timestamp, the first timestamp being a temporary timestamp corresponding to the first transaction, the first time stamp being converted from the temporary timestamp to a final timestamp by at least performing a commit operation with respect to the first transaction, and the converting from the temporary timestamp to the final timestamp comprising:
entering a commit lock;
determining a commit timestamp by at least increasing, by a first increment, the value of the commit timestamp generator;
issuing a write memory barrier;
setting, based at least on the commit timestamp, the final timestamp for the first record;
increasing, by a second increment, the value of the commit timestamp generator value; and
releasing the commit lock; and;

determining that the first record is available as part of a consistent view for the second transaction, the determining being based at least on a second timestamp of the consistent view being higher than the first timestamp of the first record; and
in response to determining that the first record is available as part of the consistent view for the second transaction, including the first record in the consistent view for the second transaction, the inclusion of the first record in the consistent view enabling the first record to be accessed by the second transaction.

8. The computer program product of claim 7 , wherein the first transaction and/or the second transaction are associated with a corresponding transaction control block index that is specific to each transaction.

9. The computer program product of claim 7 , wherein the final timestamp corresponds to a value of a commit timestamp generator.

10. The computer program product of claim 9 , wherein the operations further comprise:
selectively locking the commit timestamp generator to at least prevent the commit timestamp generator from issuing additional timestamps.

11. The computer program product of claim 7 , wherein the database comprises an in-memory database.

12. The computer program product of claim 11 , wherein the in-memory database is an in-memory columnar database storing data in columns.

13. A system comprising:
at least one hardware data processor; and
memory storing instructions which, when executed by the at least one hardware data processor forming part of at least one computing device, result in operations comprising:
handling a first transaction in a database, the first transaction comprising a plurality of operations on at least a first record in the database, and the first transaction being handled concurrently with at least a second transaction;
assigning, to the first record, a first timestamp, the first timestamp being a temporary timestamp corresponding to the first transaction, the first timestamp being converted from the temporary to a final timestamp by at least performing a commit operation with respect to the first transaction, and the converting from the temporary timestamp to the final timestamp comprising:
entering a commit lock;
determining a commit timestamp by at least increasing, by a first increment, the value of the commit timestamp generator;
issuing a write memory barrier;
setting, based at least on the commit timestamp, the final timestamp for the first record;
increasing, by a second increment, the value of the commit timestamp generator value; and
releasing the commit lock; and;

determining that the first record is available as part of a consistent view for the second transaction, the determining being based at least on a second timestamp of the consistent view being higher than the first timestamp of the first record; and
in response to determining that the first record is available as part of the consistent view for the second transaction, including the first record in the consistent view for the second transaction, the inclusion of the first record in the consistent view enabling the first record to be accessed by the second transaction.

14. The system of claim 13 , wherein the first transaction and/or the second transaction are associated with a corresponding transaction control block index that is specific to each transaction.

15. The system of claim 13 , wherein the final timestamp corresponds to a value of a commit timestamp generator.

16. The system of claim 15 , wherein the operations further comprise:
selectively locking the commit timestamp generator to at least prevent the commit timestamp generator from issuing additional timestamps.

17. The system of claim 13 , wherein the at least one processor and the memory form part of an in-memory columnar database storing data in columns.

Assignees

• Schreter Ivan
• Lee Juchang
• Andrei Mihnea
• Park Changgyoo
• Sap Se

Inventors

• Schreter Ivan
• Lee Juchang
• Andrei Mihnea
• Park Changgyoo

Classifications

• G06F17/30353

  Physics · mapped topic

• G06F17/30592 Primary

  Physics · mapped topic

• G06F16/2322 Primary

  using timestamps · CPC title

• G06F16/2365 Primary

  Ensuring data consistency and integrity · CPC title

• G06F16/283 Primary

  Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP · CPC title