#29001: postgres connection hstore support can disappear in low memory 
situations
-------------------------------------+-------------------------------------
     Reporter:  Ronan Klyne          |                    Owner:  (none)
         Type:  Bug                  |                   Status:  new
    Component:  contrib.postgres     |                  Version:  1.8
     Severity:  Normal               |               Resolution:
     Keywords:  postgres hstore      |             Triage Stage:
  signal weakref                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Ronan Klyne):

 I honestly don't know enough about the GC to explain this properly in the
 docs but I have seen the problem happen in django-hstore. I was reading
 the Django code and saw the same pattern so I pushed the same fix as a PR
 here. At the very least it seemed like a more explicit description of the
 desired effect - I don't think we would ever want this signal handler to
 be garbage collected.

 Django itself is using a module level function and django-hstore uses a
 module level singleton callable class. That's close enough that I would
 imagine that it's vulnerable to whatever peculiarity was breaking django-
 hstore, though I can't explain why the garbage collector would collect it.

 When this problem occurs it manifests as an hstore field being set to a
 string value on the Model - the dictionary deserialisation is never
 triggered.

 Maybe you just want to archive this until that situation arises in the
 wild?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29001#comment:3>
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/064.12d5fe86e580f4d97c4701623e6fe05c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to