Use asyncpg pool for the notification connection #8435
Merged
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
FirelightFlagboy
approved these changes
Sep 18, 2024
AureliaDolo
approved these changes
Sep 19, 2024
touilleMan
approved these changes
Sep 20, 2024
FirelightFlagboy
approved these changes
Sep 20, 2024
touilleMan
force-pushed
the
use-pool-for-notification-connection
branch
from
2dabc32
to
c3f3536
Compare
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.
This way, the
PARSEC_DB_MIN_CONNECTIONS/PARSEC_DB_MAX_CONNECTIONSconfiguration will correctly reflect the number of connections made to the database.