New postgres-postgis config file with an hikari cp connection pool. #9107
+126
−2
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.
When using dbcp as a connection pool, with a validation query is used to probe connections, it happens that probed connections cannot be set read-only anymore. With hikari, it is possible given that 'isolateInternalQueries' hikari configuration is set to true.
(with dbcp, 'cannot set connection read-only...' messages can be seen given that log4j-dev conf. is used)
Please also note that 7e4ec9d#diff-5035522e09ba653fd7fd93d85c31ee0cf090b4c731eeb3e7cb3c042f837e2db3R49 fix log4j-dev parsing and can make "mvn jetty:run" very verbose.
Checklist
mainbranch, backports managed with labelREADME.mdfilespom.xmldependency management. Update build documentation with intended library use and library tutorials or documentation