fix: query optimizer cache invalidation and memory leak #92
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves the robustness of the Query Optimizer cache.
1. Cache Invalidation Hardening
"users") or complex spacing. This meant thatUPDATEorDELETEoperations might not invalidate the cache, leading to stale data.execute()(write) operation occurs but no tables can be identified (e.g., complex subquery), the entire cache is cleared to guarantee consistency.2. Stats Memory Leak
statsmap grew indefinitely with every unique query string. Dynamic queries (e.g., variableINclauses) could cause OOM.statsmap size to 1000 entries with LRU-style eviction.Result: More reliable caching and stable memory usage.