Create a materialized view for userScores #272
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
dfabulich
force-pushed
the
user-scores-materialized-view
branch
from
4b2a6c6 to
9229fab
Compare
salty-horse
approved these changes
Jan 3, 2024
dfabulich
force-pushed
the
user-scores-materialized-view
branch
from
9229fab to
15208d2
Compare
dfabulich
force-pushed
the
user-scores-materialized-view
branch
from
15208d2 to
ddf68cc
Compare
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.
Rather than using a complicated system of triggers like I did in #270, for this one, I think it's fine to just refresh the materialized view via cron running once every five minutes. (The query is supposed to take less than a second, when the system isn't overloaded.)
Cooking up the triggers would require us to manage triggers on all of these tables:
This is the simplest thing that could possibly work.