Use keyset (cursor) pagination instead of large OFFSET

Use keyset (cursor) pagination instead of large OFFSET | BeforeMerge Rules | BeforeMerge

Why this matters

OFFSET 100000 still reads and throws away 100,000 rows before returning the page, so latency grows with page depth. Keyset pagination seeks directly using the last row's key and an index, giving constant-time pages.

-- Bad: scans and discards 100k rows
SELECT * FROM events ORDER BY id LIMIT 20 OFFSET 100000;

-- Good: seek from the last id seen, uses the index
SELECT * FROM events WHERE id > $last_id ORDER BY id LIMIT 20;

Why This Matters

Related Rules

Catch this automatically on every PR

Why this matters