Database Record Reuse via Journal Log Page Co-location
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database management systems face inefficiencies in reusing deleted records due to the need for separate I/O operations to access and write these records, especially when they are not located on the same page as current modifications within a journal log bundle.
Innovation Solution
The method involves identifying and reusing deleted database records located on the same page as modified records within a journal log bundle, allowing for insertion of new records using these deleted records, thereby reducing the number of I/O operations required.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If deleted database records are reused by performing separate I/O operations to access and write them, then the database record reuse function is achieved, but the I/O operation efficiency deteriorates due to multiple separate operations
Solution Approach 1:
The patent merges the I/O operations for accessing modified records and writing deleted records by co-locating them on the same page. When a page contains both modified records (from journal log bundle) and deleted records (marked for reuse), the system performs a single I/O operation to access the page and simultaneously applies both the modifications and reuses the deleted records, eliminating the need for separate I/O operations.
Solution Approach 2:
The patent performs preliminary actions by pre-identifying and marking deleted records for reuse before the actual insert operation. The system scans the database page in advance, identifies deleted records that can be reused, and prepares them for reuse by clearing their deleted status. This preliminary preparation allows the reuse operation to be integrated into the same I/O operation as the insert, reducing subsequent I/O overhead.
2Ease of operation
If deleted records are reused without checking page location, then the reuse operation is simpler, but the number of I/O operations increases due to accessing records on different pages
Solution Approach 1:
The patent applies local quality by making the reuse operation location-dependent. Instead of uniformly reusing any deleted record regardless of location, the system specifically targets deleted records that are located on the same page as modified records in the journal log bundle. This localized approach ensures that reuse operations benefit from co-located I/O, improving throughput while maintaining operational simplicity through page-level scanning.
3Reliability
If separate I/O operations are performed for accessing and writing deleted records, then data integrity is maintained through distinct operations, but the overall system performance deteriorates
Solution Approach 1:
The patent merges multiple I/O operations into a single operation by co-locating modified records and deleted records on the same database page. The system performs one I/O operation to access the page, then simultaneously applies modifications from the journal log bundle and reuses the deleted records by clearing their deleted status. This merging maintains data integrity through atomic page-level operations while significantly improving system performance by eliminating redundant I/O cycles.
Data Source
AI summary
A computer-implemented method for reusing deleted database records includes, receiving, by a database manager executing within a computing device, a first query request to insert, into a database table, a first set of database records. The database manager identifies a first set of entries within a journal log bundle. The database manager also determines, in response to identifying a first set of entries, that there is a third set of deleted database records located on a same page as a second set of database records. The database manager also, in response to determining that there is a third set of deleted database records located on a same page as the second set of database records, inserts into the database table the first set of database records using the third set of deleted database records.