Pool violation after v1.13
eyounis opened this issue · 2 comments
eyounis commented
Based on my testing, I think pgmoon now violates the pool separation since v.1.14 when the decision was made to hold on to the socket object after disconnect. When making subsequent connection regardless of the pool name provided, you get the same object.
eyounis commented
after a lot of digging through the code, I found out the issue: pool: @config.pool_name
it's now expecting pool_name setting instead of pool, which is wrong per the documentation
eyounis commented
additionally I am getting "missing database for connect" on subsequent connections that doesn't happen in v1.13