Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pool violation after v1.13 #142

Open
eyounis opened this issue Jul 8, 2023 · 2 comments
Open

Pool violation after v1.13 #142

eyounis opened this issue Jul 8, 2023 · 2 comments

Comments

@eyounis
Copy link

eyounis commented Jul 8, 2023

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
Copy link
Author

eyounis commented Jul 8, 2023

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
Copy link
Author

eyounis commented Jul 13, 2023

additionally I am getting "missing database for connect" on subsequent connections that doesn't happen in v1.13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eyounis