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

PostgreSQL connection leakage #328

Open
ArtemSBulgakov opened this issue Nov 25, 2024 · 0 comments
Open

PostgreSQL connection leakage #328

ArtemSBulgakov opened this issue Nov 25, 2024 · 0 comments
Assignees
@dantetemplar
Labels
bug Something isn't working

Comments

@ArtemSBulgakov
Copy link
Member

Django somehow leaks Postgres connections up to 50. As a result, there is a memory leak due to many TCP sockets in use.

It would be great to use some kind of connection pool.
@ArtemSBulgakov ArtemSBulgakov added the bug Something isn't working label Nov 25, 2024
@ArtemSBulgakov ArtemSBulgakov moved this to 📋 Backlog in InNoHassle Nov 25, 2024
@dantetemplar dantetemplar self-assigned this Nov 25, 2024
@dantetemplar dantetemplar moved this from 📋 Backlog to 🏗 In progress in InNoHassle Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dantetemplar dantetemplar

Labels
bug Something isn't working
Projects
InNoHassle
Status: 🏗 In progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ArtemSBulgakov @dantetemplar