Method and system for performing concurrency control in a relational database

• US 20040199549A1
• Filed: 12/11/2003
• Published: 10/07/2004
• Est. Priority Date: 06/25/2001
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Oksanen, Kenneth
• Application Number:
  US10/480,274
• Publication Number:
  US 20040199549A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466

Abstract

The present invention relates to a method and a system for performing concurrency control in a relational database. A checklist of read and/or write events served during a transaction is generated, and concurrent checklists are analyzed to determine whether they can be serialized. The transaction is then commited based on the result of said analyzing step. Thus, nothing is written to the database by the transactions when they obtain elements from the database, such that concurrency control is possible for system employing a copy-on-write policy.

Claims

1. A method for performing concurrency control in a relational database, said method comprising the steps of:

a) obtaining a snapshot of said database for a transaction;

b) generating a checklist of read and/or write events served during a transaction;

c) analyzing concurrent checklists to determine whether they can be serialized;

d) committing said transaction based on the result of said analyzing step; and

e) generating a new snapshot of said database based on the result of said committing step.

2. A method according to claim 1, wherein said analyzing step is based on a checking operation as to whether database elements mentioned in said concurrent checklists are consistent.

3. A method according to claim 2, wherein said checking operation is based on database element identities and/or timestamps collected to said concurrent checklists.

4. A method according to any one of the preceding claim 1, wherein said events are based on a copy-on-write policy.

5. A method according to claim 1, further comprising the steps of requesting a snapshot of said relational database for read-only transactions, returning an updated snapshot for updating transactions, and storing snapshot requests in a snapshot request queue.

6. A method according to claim 5, further comprising the steps of requesting a snapshot in an exclusive mode for an updating transaction request in an autocommit mode, and sending a generated snapshot to the first entry of said snapshot request queue.

7. A method according to claim 6, wherein incoming checklists are queued until no transaction uses said database in an exclusive mode.

8. A method according to claim 1, wherein said analyzing step comprises the step of validating said concurrent checklists against a current database snapshot.

9. A method according to claim 8, wherein said committing step comprises the steps of updating said current database snapshot and reporting successful commitment.

10. A method according to claim 1, comprising the step of discarding additions to said checklist if said checklist exceeds a predetermined length.

11. A system for performing concurrency control in a relational database, said system comprising:

a) managing means (30) for maintaining said relational database based on transaction statements received from clients (50); and

b) transaction means (20-1 to 20-N) for generating a checklist of read and/or write events served during a transaction, and for sending said checklist to said managing means (30) if said transaction request is to be comitted;

c) wherein said managing means (30) is arranged to analyze concurrent checklists to determine whether they can be serialized, and to commit said transaction based on the result of said analyzing step.

12. A system according to claim 11, wherein said manager means (30) is arranged to analyze said concurrent checklists based on a checking operation as to whether database elements mentioned in said concurrent checklists are consistent.

13. A system according to claim 11, wherein said manager means (30) is arranged to validate said concurrent checklists against a current database snapshot, to perform an update of said current snapshot, to discard the old snapshot, and to report successful commitment, if it has not detected any conflict.

14. A system according to claim 11 wherein said system is an SQL-based server.