Make the database health probe constant cost - #31
Merged
Conversation
Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
|
Vercel preview for |
connortsui20
marked this pull request as ready for review
September 8, 2026 16:11
connortsui20
enabled auto-merge (squash)
September 8, 2026 16:14
robert3005
approved these changes
Sep 9, 2026
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
2 participants
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.
Replaces six table counts and the latest-commit lookup with one
SELECT 1, so health probes no longer scan benchmark data. Returns uncached 200/503 responses containing onlystatus,build_sha, andschema_version. Focused unit and Postgres integration tests, lint, formatting, and a production build pass.