fix(librisxl-tools): analyze tables after pg_restore #1688
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
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.
We had some complaints about the
/_findholdendpoint on STG being extremely slow after reimporting data from prod. Turns out Postgresql hadn't updated table statistics (yet), so the query plan was whack, and some query took >10000 ms to execute instead of 1-2 ms. Autovacuum or periodicANALYZEshould take care of this, but apparently not always quickly enough, so let's runANALYZEmanually on all tables directly after restoring data. It only takes a few seconds.