Repository navigation
Fix sponsor audience timeouts with a verified covering index - #171
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
filiksyos
changed the title
filiksyos
marked this pull request as ready for review
October 11, 2026 05:50
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
This branch was successfully deployed
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 automatic visitor counter fell back to an owner snapshot because its database query exceeded the existing 8-second API limit.
The equivalent single-scan query and approved concurrent covering index are now installed. Public /sponsor shows '35K visitors last month' and 'Monthly traffic updates hourly'; Supabase REST logs confirm HTTP 200. September totals remain exactly 35,087. This PR records reproducible SQL, regression coverage and deployment evidence; it does not change frontend or access permissions.
Validation: 43 sponsor/library tests, TypeScript, targeted lint and diff check pass. Synthetic SQL checks pass; fixed-time comparison found zero differences across every aggregate field. Index is valid/ready (~9.8MB). Four actual service-role function runs stayed below the unchanged 8-second timeout: 7.491, 5.461, 3.497 and 1.718 seconds. Cold-cache margin remains limited because some recent pages require heap visibility checks; no timeout or maintenance settings were changed.
SECURITY INVOKER, fixed filters, service_role-only execution and anon/authenticated denial are unchanged. The index was created through standalone SQL because the migration wrapper cannot execute CREATE INDEX CONCURRENTLY. No raw data, credentials or unrelated library RPC changes.