Add support for DB_SSLMODE=require in streaming API #25483
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.
There were several attempts to fix #11445, the latest I've found in #23960 (which is a fix for #21431).
Sadly the way it was done is by adding
no-verify
instead ofrequire
. Whileno-verify
is supported by the node module, it is not supported by any other standard libraries, including the ruby ones.Since there is no distiction made in documentation between
DB_SSLMODE
for streaming and the other backends and it's assumed the same values are used everywhere, commonly used values need to be supported.A lot of workarounds already exist that essentially do the same.
Fixes #11445
Fixes #26034