misc(events) - Setup more aggressive autovacuum_vacuum_scale_factor setting for events #2360
Conversation
This file contains 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
nudded
force-pushed
the
misc-db-add-autovacuum-settings
branch
from
728d5d2
to
c30407f
Compare
nudded
force-pushed
the
misc-db-add-autovacuum-settings
branch
from
c30407f
to
5e59b92
Compare
jdenquin
approved these changes
Aug 2, 2024
abdussamadbello
pushed a commit
to abdussamadbello/lago-api
that referenced
this pull request
Aug 8, 2024
…etting for events (getlago#2360) ## Description Default postgres autovacuum settings are a bit too defensive for our use-cases. We require frequent vacuuming of the events table, mostly to keep the visibility map of the events table up to date.
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.
Description
Default postgres autovacuum settings are a bit too defensive for our use-cases. We require frequent vacuuming of the events table, mostly to keep the visibility map of the events table up to date.