fix(query): ensure that open connection are killed after timeout #946
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
avallete
force-pushed
the
fix/query-timeout-connection-closing
branch
2 times, most recently
from
0125e82 to
9919c68
Compare
Pull Request Test Coverage Report for Build 15137718772Details
💛 - Coveralls |
Without statement_timeout set, the query_timeout wont always kill the underlying database query connection leading to possible connections exhaustions
avallete
force-pushed
the
fix/query-timeout-connection-closing
branch
from
9919c68 to
5434754
Compare
soedirgo
approved these changes
May 20, 2025
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Without statement_timeout set, the query_timeout wont always kill the underlying database query connection leading to possible connections exhaustions