fix(db-postgres): too many clients already, cannot read properties 'transaction' of undefined #6338
Conversation
This file contains 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
JessChowdhury
pushed a commit
that referenced
this pull request
May 14, 2024
…ransaction' of undefined (#6338)
JessChowdhury
pushed a commit
that referenced
this pull request
May 14, 2024
…ransaction' of undefined (#6338)
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
This PR aims to solve a few misc. issues related to Postgres and HMR.
First, we may have been creating a new connection each time HMR fired. We now re-use existing connections so that connection pools aren't exhausted.
Second, we now track Drizzle initialization across multiple invocations, so that if HMR is triggered, but there was already an operation in flight, Payload will wait for initialization before beginning a new transaction.