Offset Pagination
Offset pagination skips a chosen number of sorted records and returns the next page up to a set size.
Another example
An admin searches a stable nightly customer snapshot with `limit=50&offset=100` and jumps to page 3. The sort uses `customer_id` to break ties in a fixed way. New live records can move pages, so a real-time activity stream uses cursors instead.
Main parts
- 01Stable sort
- 02Offset and limit
- 03Page metadata
Use it when
Use it for a small or medium, stable set when page numbers and jumping to any page matter. Measure the query cost.
Do not use it when
Avoid very large offsets or fast-changing lists. The scan can get slow, and records may repeat or vanish between pages.
Name used in code
deterministic ORDER BY + LIMIT page_size + OFFSET n Before you ship
Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback.
Outcome: Design or review Offset Pagination for this system while keeping data correct, secure, and easy to operate. User context: An admin searches a stable nightly customer snapshot with `limit=50&offset=100` and jumps to page 3. The sort uses `customer_id` to break ties in a fixed way. New live records can move pages, so a real-time activity stream uses cursors instead. Technical concept or control: Offset Pagination. Why it fits: Use it for a small or medium, stable set when page numbers and jumping to any page matter. Measure the query cost. Do not use it when: Avoid very large offsets or fast-changing lists. The scan can get slow, and records may repeat or vanish between pages. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.
Check this request
Review the current use of Offset Pagination. Definition: Offset pagination skips a chosen number of sorted records and returns the next page up to a set size. Release checks: Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.