#31905: ASGI: Dead persistent postgres connections are not closed when the
database
is accessed in middleware
-------------------------------------+-------------------------------------
Reporter: Michael Galler | Owner: Michael
| Galler
Type: Bug | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: ASGI Postgres | Triage Stage: Ready for
Persistent | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"b6d2419120598c6643e16a9b309258a6e9c2a736" b6d2419]:
{{{
#!CommitTicketReference repository=""
revision="b6d2419120598c6643e16a9b309258a6e9c2a736"
[3.1.x] Fixed #31905 -- Made MiddlewareMixin call
process_request()/process_response() with thread sensitive.
Co-authored-by: Carlton Gibson <carlton.gib...@noumenal.es>
Backport of 547a07fa7ec4364ea9ecd2aabfdd16ee4c63003c from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31905#comment:17>
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/065.f468a04b8e77483789a9c222aa9e503c%40djangoproject.com.
