[DBM] Update troubleshooting pg_stat_statements not in search_path #16072
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
Preview links (active after the
|
maycmlee
reviewed
Nov 29, 2022
content/en/database_monitoring/setup_postgres/troubleshooting.md
Outdated
Show resolved
Hide resolved
content/en/database_monitoring/setup_postgres/troubleshooting.md
Outdated
Show resolved
Hide resolved
content/en/database_monitoring/setup_postgres/troubleshooting.md
Outdated
Show resolved
Hide resolved
Co-authored-by: May Lee <may.lee@datadoghq.com>
maycmlee
approved these changes
Nov 30, 2022
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?
Motivation
Explains how to diagnose an edge case where pg_stat_statements is not accessible to the datadog user in dbm.
Additional Notes
Reviewer checklist