-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql: fix prepared statement query summary #83673
sql: fix prepared statement query summary #83673
Conversation
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.
Can you add tests to confirm the correct behaviour?
Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @ericharmeling)
07d2e6d
to
e8f548f
Compare
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.
Done!
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @maryliag)
e8f548f
to
9bc1f3c
Compare
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.
Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @ericharmeling)
bors r+ |
Build failed: |
9bc1f3c
to
26cc32c
Compare
bors r- |
bors r+ |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed: |
bors retry |
Build failed (retrying...): |
Build failed (retrying...): |
26cc32c
to
fde3923
Compare
Canceled. |
bors r+ |
Build failed (retrying...): |
Build failed (retrying...): |
Looks like this PR might be flaky - the merge failed twice on bors r- |
Canceled. |
😖 you're right. I actually just built master and could not repro the behavior shown in #79152 (the issue this PR fixes). It looks like something was merged in the last week that broke |
Well this isn't entirely true. Just that the Looks like it's one of the commits in this merge: ce1b42b |
The behavior that this PR seeks to fix has changed. See #79152 (comment). |
This commit sets the StmtSummary metadata field for prepared statements to the StatementSummary value in the prepared statement metadata for prepared statements at execution. Fixes cockroachdb#79152. Release note (bug fix): Previously, the querySummary metadata field in the crdb_internal.statement_statistics table was inconsistent with the query metadata field for executed prepared statements. These fields are now consistent for prepared statements.
fde3923
to
377e6fd
Compare
Looks like the test failure here (Example_demo_locality) is flaky |
bors r+ |
Build succeeded: |
@ericharmeling can you backport this to 22.1? |
This commit sets the StmtSummary metadata field for prepared
statements to the StatementSummary value in the prepared statement
metadata for prepared statements at execution.
Fixes #79152.
Release note (bug fix): Previously, the querySummary metadata field in
the crdb_internal.statement_statistics table was inconsistent with the
query metadata field for executed prepared statements. These fields
are now consistent for prepared statements.