Skipping to Page 900 With an Offset Makes the Engine Produce and Discard 18,000 Rows
Rests on rows-touched and on multi-column index ordering, and is the clearest case in the sub-domain of a statement that is fast on every developer machine and slow only under real use. The curation's outcome is about an application under real traffic, and deep pagination is where a list endpoint quietly becomes the heaviest thing the database does. The trade it teaches — constant cost against losing arbitrary page jumps — is a decision, not a rule.
Questions this Concept answers
- Besides its cost, what correctness problem does offset paging carry?
Keyset Pagination Instead of OFFSET for Deep Pages in SQL Databases
Keyset pagination locates a page boundary by the ordered key values of the last row already returned, whereas offset pagination locates it by counting rows from the start of the result set; because t…