-
Notifications
You must be signed in to change notification settings - Fork 3
Normalize executor and utility query text with $N placeholders #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
iskakaushik
wants to merge
8
commits into
main
Choose a base branch
from
feat/query-normalization
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
35e0737
Normalize query text: replace literal constants with $N placeholders
iskakaushik af6b557
Fix clang-format violations in query_normalize.cc
iskakaushik 3c4aeaf
Fix normalization state handling and harden TAP waits
iskakaushik 3170383
Fix nested query normalization reuse
iskakaushik 10979da
Add PG16/17 normalization compatibility
iskakaushik eb15e83
Scope query normalization out of error capture
iskakaushik ed3b62f
Hash normalized statement identity lookups
iskakaushik 01477e5
Use statement key in query text copy helpers
iskakaushik File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
normalized_queryis a single per-backend buffer that can become stale or be overwritten before it is consumed. In particular: (1)PschPostParseAnalyze()can run for statements that later hit the early-return path inPschExecutorEnd()(e.g.queryId == 0), leavingnormalized_queryset; the next captured query will then incorrectly use this stale normalized text. (2) nested statements (SPI / functions) can overwritenormalized_querybefore the outer statement reachesExecutorEnd, causing the outer event to lose normalization or pick up the inner query’s text. Consider storing normalized text in a stack keyed bynesting_level, or in a small per-backend map keyed byqueryId/statement identity, and ensure the entry is removed on all completion paths (including thePschExecutorEnd()early return and utility paths).