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
37220	Paginator solutions for when default paginator encounters scaling issues	Harvey Bellini	Harvey Bellini	"The new paginator provides a way to navigate results without performing a COUNT(*) query, instead determining the existence of a ""next page"" by fetching `N + 1` items.

**Problem**

On large PostgreSQL or MySQL tables, `SELECT COUNT(*)` requires a full or partial index scan that scales linearly with data size. Even if the actual data fetch is fast (via indexed slicing), the Paginator is forced to wait for the count to:

- Validate the page number
- Determine if a ""next"" page exists
- Calculate the total number of pages for the UI

In many modern UIs (like ""Infinite Scroll"" or ""Next/Prev"" only navigation), the total page count is unnecessary and actively hurts performance.

https://github.com/django/new-features/issues/136"	New feature	assigned	Core (Other)	6.0	Normal			Carlton Gibson Frank Wiles Lily Foote Tim Schilling	Someday/Maybe	0	0	0	0	0	0