#31419: Django Postgres memory leak
-------------------------------------+-------------------------------------
Reporter: Francesco Meli | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: postgresl memory- | Triage Stage:
leak | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
Django keeps a reference to all executed queries in a ring buffer when
`settings.DEBUG = True`
From `DEBUG` [https://docs.djangoproject.com/en/3.0/ref/settings/#debug
documentation]
> It is also important to remember that when running with DEBUG turned on,
Django will remember every SQL query it executes. This is useful when
you’re debugging, but it’ll rapidly consume memory on a production server.
Please reopen if you can reproduce without `settings.DEBUG` and please
avoid using this bug tracker as a second tier support channel.
--
Ticket URL: <https://code.djangoproject.com/ticket/31419#comment:1>
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/066.a5d5b1d13f9cd960c329e586f408e1ae%40djangoproject.com.
