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

Mitigate proliferation of idle connections #730

Closed

joeflack4 opened this issue Mar 13, 2024 · 1 comment · May be fixed by #729

Assignees

Labels

bug performance

Milestone

Member

joeflack4 commented Mar 13, 2024 •

edited

Loading

Overview

This is not so much of a big problem anymore, following #661 and the close of #667. However, this is still something we may want to address.

Additional notes

Related

Possibly addressed by:

Mitigate proliferation of idle connections: SqlAlchemy Con --> Engine #729

Problem is not bad now, but when it gets out of control, it leads to:

FATAL: remaining connection slots are reserved for non-replication superuser connections #723

joeflack4 added bug performance labels

joeflack4 assigned joeflack4 and Sigfried

joeflack4 added this to TermHub

github-project-automation bot moved this to Backlog in TermHub

joeflack4 mentioned this issue

FATAL: remaining connection slots are reserved for non-replication superuser connections #723

Closed

2 tasks

joeflack4 linked a pull request

that will close this issue

Mitigate proliferation of idle connections: SqlAlchemy Con --> Engine #729

Draft

joeflack4 added this to the Unplanned milestone

Member Author

joeflack4 commented Apr 23, 2024

Going to close this; being superseded by #740

joeflack4 closed this as completed

github-project-automation bot moved this from Backlog to Done in TermHub

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment