#31637: Registering database connections for cleanup on fork
-------------------------------------+-------------------------------------
Reporter: Aarni Koskela | Owner: Josh
| Thomas
Type: New feature | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jake Howard):
* cc: Jake Howard (added)
Comment:
If 2 processes have the same descriptor open, they //should// close
separately, although it's technically possible that a "hang-up" message is
sent to the server before closing which causes it to close the connection
to the other process too (I'm not sure if / which engines do this).
Handling any post-`fork` closing as part of the backend would at least
allow backend maintainers to modify the behaviour if a database engine
does work that way.
This probably comes up more often than 4 years ago due to `manage.py test
--parallel`, which uses `fork` (usually). Disabling pooling in tests is a
semi-valid work-around, although no-longer fully representative.
--
Ticket URL: <https://code.djangoproject.com/ticket/31637#comment:9>
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/0107019e40e285a5-520c2859-8915-4ca1-907b-bd5ce42df638-000000%40eu-central-1.amazonses.com.
