#35672: Using database connection pooling, threads do not return the connection
-------------------------------------+-------------------------------------
Reporter: André S. Hansen | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Florian Apolloner):
* resolution: => invalid
* status: new => closed
Comment:
Ok, I will close this as invalid then.
> The documentation https://docs.djangoproject.com/en/5.1/ref/databases/
could do well addressing this case. But i guess you can close this ticket.
Don't the caveats in
https://docs.djangoproject.com/en/5.1/ref/databases/#caveats mention your
case exactly:
> If a connection is created in a long-running process, outside of
Django’s request-response cycle, the connection will remain open until
explicitly closed, or timeout occurs. You can use
django.db.close_old_connections() to close all old or unusable
connections.
If you can think of a better wording please open a PR; we don't need
tickets for doc improvements usually.
--
Ticket URL: <https://code.djangoproject.com/ticket/35672#comment:15>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107019166c1e44d-9cfab9b3-9437-47d6-9b78-7ba76847a192-000000%40eu-central-1.amazonses.com.
