#29001: postgres connection hstore support can disappear in low memory
situations
-------------------------------------+-------------------------------------
Reporter: Ronan | Owner: (none)
Klyne |
Type: Bug | Status: new
Component: | Version: 1.8
contrib.postgres | Keywords: postgres hstore
Severity: Normal | signal weakref
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
Present in 1.8 and master. Probably versions between but I haven't checked
them all
In order to correctly handle hstore data on new connections Django
registers a signal handler to the `connection_created` signal.
This signal is created as a weakref and can be garbage collected, causing
all future connections to misbehave when receiving hstore data from
Postgres.
This problem has also been seen and fixed in `django-hstore` -
https://github.com/djangonauts/django-hstore/pull/128
--
Ticket URL: <https://code.djangoproject.com/ticket/29001>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.f8ebde0949effe93d9dc34a08198dd4b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
