Support TLS PostgreSQL connections in notification_listener #3503
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.
Hi, this PR implements TLS PSQL connections support for the
notification_listener
, as various managed database providers allow encrypted connections only, and it is generally a bad idea to disable encryption.Related issue: #2097
With these changes it is possible to connect to databases with both TLS support and without. Please note that certificate verification is currently disabled, because it fits my use-case, and I don't have any experience with Rust whatsoever to make it configurable to support more use-cases. So I would be grateful if someone takes it over from here.
You can test it e.g. locally when running Postgres with the following command:
And monitor Postgres connections with the following command: