[Postgres] hard limit on pg count metric #2575
Merged
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.
Counting the number of tables to provide the
postgresql.table.count
metric can be very expensive, especially on large clusters.This PR contains two changes to mitigate the impact of a slow count:
postgres.yaml
fileFor backward compatibility, the metric is still collected by default
Notice: couldn't provide an integration test for the hard limit feature because the strings containing the SQL code are class fields evaluated at import time.