Selective Database Cache Removal Using ENTRY_HASH Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems face inefficiencies in managing cache entries, particularly when multiple entries are generated, as they often require clearing all entries of a specific type, which is resource-intensive and inefficient, especially when only a specific cache entry needs to be refreshed or removed due to memory load or source table modifications.
Innovation Solution
Introduce a Selective Cache Entry Removal feature using an ENTRY_HASH column in the cache entry system view, allowing users to specify and remove individual cache entries through an SQL statement, ensuring efficient removal of problematic entries while maintaining system performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If all cache entries of a specific type are cleared to remove problematic entries, then the harmful effect of stale cache data is eliminated, but resource consumption increases and system efficiency decreases
Solution Approach 1:
The patent segments the cache entry removal operation by introducing a unique ENTRY_HASH column that identifies individual cache entries. This allows the system to remove only specific problematic entries (segmented removal) rather than clearing all entries of a cache type, thereby eliminating stale data while preserving useful cached results and maintaining system efficiency.
2Reliability
If all cache entries are cleared to ensure data freshness, then data reliability is improved, but memory consumption and processing overhead increase
Solution Approach 1:
The patent extracts the identification mechanism (ENTRY_HASH column) from the general cache management system, enabling selective removal of only those specific cache entries that need refreshing. This extraction allows the system to maintain data reliability by removing stale entries without the energy cost of clearing the entire cache, as only problematic entries are targeted for removal.
3Ease of operation
If selective cache entry removal is implemented without a unique identifier system, then system complexity is reduced, but the ability to target specific entries for removal is lost
Solution Approach 1:
The patent introduces an intermediary element (ENTRY_HASH column) that mediates between the cache storage system and the removal operation. This unique identifier acts as a key that enables precise targeting of specific cache entries for removal, providing selective entry removal capability while maintaining relatively simple implementation through the use of a straightforward hash-based identification system.
Data Source
AI summary
A database management system generates a cache entry system view of a database cache. Also, a new column is generated for the cache entry system view, where the new column is an ENTRY_HASH column to identify each entry of the database cache. In an example, the database management system detects a request to remove a given entry of the database cache, where the request includes a given ENTRY_HASH value to locate the given entry of the database cache. In response to receiving the request, the database management system identifies the given entry of the database cache based on the given ENTRY_HASH value. Then, the database management system removes the given entry of the database cache. Also, the database management system notifies a cache manager that the given entry has been removed.