id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36534	Problem Statement: Spike in PostgreSQL Connections After Upgrading Django from 3.2 to 5.2 Despite CONN_MAX_AGE = 10	ps018w		"After upgrading our Django application from version 3.2 to 5.2, we started observing unexpected spikes in active PostgreSQL database connections. This issue arises despite having CONN_MAX_AGE set to 10, which should allow persistent connections to be reused within a 10-second window, thereby preventing rapid connection churn.

Current Database Configuration:

DATABASES ={""default"":env.db(""DATABASE_URL"",default=""postgres://localhost/test""), } 
DATABASES[""default""][""ATOMIC_REQUESTS""] = False 
DATABASES[""default""][""CONN_MAX_AGE""] = 10

The connection spike behavior was not observed prior to the upgrade, indicating a possible change in how Django 5.2 manages database connections, or a change in default behavior for connection pooling or request handling."	New feature	closed	Database layer (models, ORM)	5.2	Release blocker	needsinfo		ps018w	Unreviewed	0	0	0	0	0	0