Include schema in filter for indexes #17480
Merged
Conversation
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
Test Results 16 files 16 suites 21m 28s ⏱️ Results for commit b83cf97. ♻️ This comment has been updated with latest results. |
lu-zhengda
approved these changes
Apr 29, 2024
steveny91
approved these changes
Apr 29, 2024
sethsamuel
deleted the
seth.samuel/DBMON-3986-Postgres-integration-is-incorrectly-querying-for-indexes-across-all-schemas
branch
datadog-agent-integrations-bot bot
pushed a commit
that referenced
this pull request
Apr 29, 2024
(cherry picked from commit 3d4357c)
4 tasks
Kyle-Neale
pushed a commit
that referenced
this pull request
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Fixes a bug where multiple schemas with tables of the same name were reporting all indexes across schemas. Also fixes a similar bug for partitions.
Motivation
Indexes should be reported per table/schema.
Additional Notes
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged