feat(engagement): add post_engagement_daily materialized view + tests (#181)#233
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
1 participant
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.
Materialize per-(post_id, day) metrics with an hourly pg_cron refresh (0 * * * *, max 1h dashboard lag) and a unique (post_id, day) index for REFRESH ... CONCURRENTLY. The MV lives in the
privateschema — materialized views support neither RLS nor security_invoker — and reads go through public.post_engagement_daily, an owner-rights view guarded by is_manager().Sources are pre-aggregated and joined over a spine to avoid fan-out and to keep click_rate NULL when a day has no readers. Add fixed-dataset pgTAP covering the aggregation, the zero case, the index, the cron job and RBAC.
Closes #181