#34865: DatabaseWrapper are not GC and connections are not closed
-------------------------------------+-------------------------------------
Reporter: Fábio Domingues | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Fábio Domingues):
Replying to [comment:1 Mariusz Felisiak]:
> Fabio, thanks for the report. Is there a reason to open a new ticket and
don't add your findings in the #33497? As far as I'm aware, this is a
duplicate.
Fixing this memory leak will not solve the problem of the persistent
connections not been reuse, only the fact that they will not pill up (and
starve the DB) if inaccessible.
But I'm new here, still learning. Should I move the findings to #33497?
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018abc70950d-0f49ad69-8984-4fae-a458-517ae1b8623e-000000%40eu-central-1.amazonses.com.
