Background job to log psql table bloat stats#6203
Merged
Conversation
847a03a to
a3dbfdc
Compare
a3dbfdc to
9c3ee2a
Compare
9c3ee2a to
a0b2aca
Compare
93db7e5 to
d1cf2c0
Compare
zachmargolis
approved these changes
Apr 14, 2022
Contributor
zachmargolis
left a comment
There was a problem hiding this comment.
Two last changes we need and then it's good to go
d1cf2c0 to
ac4eb45
Compare
changelog: Internal, Database, Background job to log psql table bloat stats
ac4eb45 to
5a58679
Compare
Contributor
Author
|
Thanks @mitchellhenke I also noticed that Changing it to |
Contributor
Author
|
🚢 |
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
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.


The title sums it up, this is in support of https://github.com/18F/identity-devops/issues/4175 to help us log psql table bloat stats. This will help us better calculate how often we need to run table vacuums and if the current configuration is able to keep up with the churn.