#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
-------------------------------------+-------------------------------------
Changes (by Tim Graham):

 * easy:  1 => 0


Comment:

 I don't know much about how garbage collection works in Python, but if
 this is indeed the correct solution, then perhaps some clarifications to
 
[https://docs.djangoproject.com/en/dev/topics/signals/#django.dispatch.Signal.connect
 Django's documentation] would be useful. It says,"Django stores signal
 handlers as weak references by default. Thus, if your receiver is a local
 function, it may be garbage collected." but my understanding is that the
 receiver here (`register_type_handlers`) isn't a local function.

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

Reply via email to