Skip to content

Pool violation after v1.13 #142

Open
@eyounis

Description

@eyounis

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions