-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](jdbc catalog) Fix connection leak in PostgreSQL JDBC client #49568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Member
Author
|
run buildall |
TPC-H: Total hot run time: 33939 ms |
TPC-DS: Total hot run time: 186944 ms |
ClickBench: Total hot run time: 31.67 s |
hubgeter
approved these changes
Apr 2, 2025
Contributor
|
PR approved by anyone and no changes requested. |
morningman
approved these changes
Apr 2, 2025
CalvinKirs
approved these changes
Apr 2, 2025
Contributor
|
PR approved by at least one committer and no changes requested. |
github-actions bot
pushed a commit
that referenced
this pull request
Apr 2, 2025
…9568) ### What problem does this PR solve? Connection leak in JdbcPostgreSQLClient when handling array types, causing PostgreSQL server error "too many clients already". ### Solution 1.Use explicit resource management instead of try-with-resources 2. Add exception handling and properly close all database resources
Closed
starocean999
pushed a commit
to starocean999/incubator-doris
that referenced
this pull request
Apr 27, 2025
koarz
pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
…ache#49568) ### What problem does this PR solve? Connection leak in JdbcPostgreSQLClient when handling array types, causing PostgreSQL server error "too many clients already". ### Solution 1.Use explicit resource management instead of try-with-resources 2. Add exception handling and properly close all database resources
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
What problem does this PR solve?
Connection leak in JdbcPostgreSQLClient when handling array types, causing PostgreSQL server error "too many clients already".
Solution
1.Use explicit resource management instead of try-with-resources
2. Add exception handling and properly close all database resources