Database Row-Version Cleaning via Selective Inspection and Marking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current solutions for creating, maintaining, and removing point-in-time (PiT) images in distributed databases are inefficient, leading to performance issues and scalability challenges.

Innovation Solution

A method for efficiently cleaning row-versions in databases by selecting eligible row-versions for inspection, classifying them as unneeded or reliant, and removing unneeded row-versions immediately while relying on the removal of related PiTs for reliant row-versions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional row-version cleaning techniques are used in distributed databases, then consistency is maintained, but performance deteriorates and scalability is limited

Engineering Contradiction:

ImproveconsistencyVSAvoidperformance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent segments the row-version cleaning process into two distinct phases: a preparation phase that identifies and marks unneeded row-versions, and a removal phase that actually deletes them. This segmentation allows the system to maintain consistency markers without immediately performing resource-intensive deletion operations, thereby improving performance while preserving reliability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary identification and marking of unneeded row-versions before actual removal. By pre-marking row-versions with removal indicators during normal transaction processing, the system avoids the need for expensive full-scans at cleanup time, thus improving performance while maintaining consistency through the preliminary marking stage.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If full row-version inspection is performed to ensure consistency, then reliability is improved, but time consumption increases

Engineering Contradiction:

ImproveconsistencyVSAvoidtime consumption

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial inspection by examining only specific row-versions that are candidates for removal, rather than performing exhaustive full-scans of all row-versions. The system uses version vectors and timestamps to identify and inspect only those row-versions that may be unneeded, reducing time consumption while maintaining sufficient reliability for consistency checks.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent replaces traditional mechanical scanning mechanisms with a marker-based identification system. Instead of physically scanning and inspecting every row-version, the system uses version vectors, timestamps, and removal markers to logically identify unneeded row-versions, significantly reducing inspection time while maintaining consistency reliability.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If resource-intensive cleaning processes are used to remove all row-versions, then database performance is improved, but resource usage increases

Engineering Contradiction:

Improvedatabase performanceVSAvoidresource usage

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent extracts and removes only the unneeded row-versions from the database, rather than performing blanket cleaning of all row-versions. By using version vectors and timestamps to identify specifically which row-versions are unneeded, the system performs targeted removal operations that improve database performance without unnecessarily consuming resources on already-useful data.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements a selective discarding mechanism where only row-versions that are truly unneeded (as determined by version vectors and timestamps) are removed. The system recovers resources by eliminating only the obsolete data while preserving useful row-versions, thus improving performance without excessive resource consumption that would result from indiscriminate cleaning.

Inventive Principle:

Principle #34Discarding and recovering

Data Source

PatentUS20250028694A1Ranging techniques for efficient cleaning of unneeded row-versions of a database

Publication Date: 2025.01.23 REGATTA DATA LTD

AI summary

In one general aspect, a method may include selecting eligible row-versions for inspection. The method may also include inspecting the selected row-versions, where the inspection results in a classification of eligible row-versions as unneeded or reliant. The method may furthermore include marking row-versions classified as unneeded as approved for immediate removal. The method may, in addition, include adding row-versions classified as reliant on cleaner structures. The method may moreover include upon detection of removal of all point-in-times (PiTs) related to a reliant row-version, deleting the reliant row-version, where the detection is performed by monitoring the cleaner structures. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.