Add support for custom tls.Config #1229
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
Doesn't run all the tests, even though they work fine locally? https://github.com/lib/pq/actions/runs/20829056100/job/59993754645 Although even locally it's not completely "fine" because tests start failing after a few test runs for some reason. I added pgpool for #1188, but It's an old container with an old version, and I have the impression it's not that widely used (there's no package on Void for example, and #1188 and #342 are the only two mentions in 14 years of pq). I'm going to say that people who want pgpool support can send a PR to properly fix it.
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.
Allow registering a custom TLS configuration, for example to use encrypted keys.
Based on #1066
Fixes #766
Fixes #789
Fixes #811
Fixes #849