Not sure if this is still the correct solution (it's been a while) but we
solved this back in the day by appending the parameter ?useBundledJdbcInfo=true
to the
DB connection URL. Makes the Postgres plugin load jdbcInfo from the plugin
bundle rather than the DB.
https://github.com/wocommunity
Hi Aaron,
for each of my instances I have two database connections to the postgres DB -
obviously one with the idle transaction and the other working one. And each
idle transaction originates from the woa startup. So your conclusion sounds
reasonable.
But I still did not find where this select
Hi Markus,
So that means you, too, have some queries that are stuck. Postgres is waiting
for you to issue a commit. As long as they live, it will not be able to vacuum
properly. When you close down the .woa, it will no longer be “idle in
transaction”
It’s a curious thing.
For me it appears t
