#34870: Memory leak when using psycopg-c with django hstore
-------------------------------------+-------------------------------------
Reporter: David Burke | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David Burke):
I'm unsure which project is at fault. The reverse could be said as - not
using Django's "django.contrib.postgres" fixes the issue, does it follow
that django is at fault. Is there something that makes you suspect psycopg
is at fault or a better place to submit an issue? In the linked sample
repo, just commenting out that one line in INSTALLED_APPS fixes it. But
then the HStore feature is no longer available from Django.
If I can strip out more code away for a more minimalist reproduction repo,
I will follow up here. It would also be more ideal to remove Celery to
rule that out.
--
Ticket URL: <https://code.djangoproject.com/ticket/34870#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ac9caf271-4c51cae6-e105-4e1e-a1b5-ef0c51c1c808-000000%40eu-central-1.amazonses.com.
