Repository navigation
fix: reuse Prisma pools in production - #519
Merged
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
 |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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.
Description
Production skipped the global Prisma cache, so separate Next.js server bundles could each create a five-connection pool. Overlapping containers exhausted Supabase’s fifteen-session pool during deployment. Cache the base client in production too, with a regression test using the real adapter.
No linked issue. This promotes the same pool fix through staging while preserving production’s newer dependencies and entire Prisma tree.
Type of change
How Has This Been Tested?
Screenshots (if applicable)
Not applicable.
Checklist
Notes for reviewers
The first replacement must avoid overlapping the old process’s duplicate pools. Publish and pull the verified image before stopping the old app, then restore rolling updates after verification. Dependencies, schema and query behavior are unchanged.