feat: migrate from psycopg2 to psycopg3 and fix connection pool issues #5497
Conversation
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
Contributor
|
Skipped: This PR does not target one of your configured branches: ( |
|
@Viste is attempting to deploy a commit to the KeepHQ Team on Vercel. A member of the Team first needs to authorize it. |
dosubot
bot
added
size:S
Replace psycopg2 with psycopg (version 3) and add comprehensive connection pool configuration to fix critical issues under high load (1000+ alerts/min) and enable PgBouncer compatibility. **Critical Issues Fixed:**
Viste
force-pushed
the
feat/migrate-psycopg2topsycopg3-and-connection-pool-issue-fix
branch
from
396f425 to
b71be2a
Compare
…on-pool-issue-fix
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.
📑 Description
close #5496