When providing a session mode pool config via session_mode_url, it's not clear that session_mode_url is parsed into a keyword list and replaces the parent config.
For example, we use the following configuration to connect to Digital Ocean's managed Postgres:
The options ssl, ssl_opts, and prepare are particularly important to our connection and are not included when generating the config (session mode pool config) from the session_mode_url.
This PR merges the session mode pool config into the parent config before passing it along. So that all the specified configuration options are used for the session mode pool, too. Which, I think, is what people probably expect when looking at the above event store configuration.
When providing a session mode pool config via
session_mode_url
, it's not clear thatsession_mode_url
is parsed into a keyword list and replaces the parent config.For example, we use the following configuration to connect to Digital Ocean's managed Postgres:
The options
ssl
,ssl_opts
, andprepare
are particularly important to our connection and are not included when generating the config (session mode pool config) from thesession_mode_url
.This PR merges the session mode pool config into the parent config before passing it along. So that all the specified configuration options are used for the session mode pool, too. Which, I think, is what people probably expect when looking at the above event store configuration.