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.

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

Operator connection leak #169

Closed
alexeyklyukin opened this issue Nov 27, 2017 · 1 comment
Closed

Operator connection leak #169

alexeyklyukin opened this issue Nov 27, 2017 · 1 comment

Comments

@alexeyklyukin
Copy link
Contributor

Apparently after the 415a7fd when creating users too many idle connections are established per each cluster, each of them corresponding to a single user and doing:

BEGIN ALTER ROLE "vhengst" RESET ALL;ALTER ROLE "vhengst" SET log_statement TO 'all'; END;

It seems that the changes actually triggered the old bug of establishing too many connections (could be that the underlying library is not limiting itself to only one), but the issue was dormant until after another bug, caused by the aforementioned request that changes the log_statement every time it goes the sync happens.

@alexeyklyukin alexeyklyukin changed the title Operator memleak Operator connection leak Nov 27, 2017
@alexeyklyukin
Copy link
Contributor Author

Fixed with 1ffe98b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant