#36534: Problem Statement: Spike in PostgreSQL Connections After Upgrading
Django
from 3.2 to 5.2 Despite CONN_MAX_AGE = 10
-------------------------------------+-------------------------------------
Reporter: ps018w | Owner: (none)
Type: New feature | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => needsinfo
* status: new => closed
Comment:
Thanks for the report. However, I don't think you've explained the issue
in enough detail to confirm a bug in Django. It's hard to say without a
sample project.
Please reopen the ticket if you can debug your issue and provide details
about why and where Django is at fault, or if you can provide a sample
project with reproducible scenario.
Note that I see you have posted on the forum
(https://forum.djangoproject.com/t/problem-statement-spike-in-postgresql-
connections-after-upgrading-django-from-3-2-to-5-2-despite-conn-max-
age-10/42146), I think it makes sense to provide more details on your
project there and debug with the community to determine what is the cause
of the spike.
--
Ticket URL: <https://code.djangoproject.com/ticket/36534#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 visit
https://groups.google.com/d/msgid/django-updates/010701986034bd17-d8291fc5-6c7c-4e8d-8f10-f8e6f09aba0f-000000%40eu-central-1.amazonses.com.
