Bound database pool waits and attach Vercel cleanup - #33
Draft
connortsui20 wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
|
Vercel preview for |
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.
Attaches the singleton pg pool to Vercel’s lifecycle hook and bounds connection and pool-slot waits to five seconds by default. Reduces the idle timeout to five seconds while preserving the 30-second statement timeout, TLS verification, and per-connection IAM tokens. Existing deployments with an idle-timeout override must lower it separately to benefit from prompt cleanup. Focused unit and Postgres tests, lint, formatting, and a production build pass, but local tests do not prove cleanup during Vercel suspension.