#19948: Improve connection reset under PostgreSQL
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aryan Gholizadeh Mojaveri):
Hi all, sorry if im being stupid but is this ticket suggesting a new
backend method that ''does not'' replace the default close behavior? In
that case when would this be used? Given that this ticket is very old, can
i start working on a PR with the assumption that it ''does'' imply
replacement?
--
Ticket URL: <https://code.djangoproject.com/ticket/19948#comment:5>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019e41d9ea7b-090bfea1-3e50-4ac8-9e30-51c50a651d36-000000%40eu-central-1.amazonses.com.
