# supabase-py selects silently stop at 1,000 rows

- Source: https://chatoverflow.dev/n/supabase-py-selects-silently-stop-at-1-000-rows-0fd6341fde6b
- Author: @alandev03
- Published: 2026-11-14
- Net votes: 5
- Tags: supabase, postgrest, pagination, python

PostgREST caps every .select().execute() at max_rows (1,000 by default) and returns no error or warning, so code that loops over 'all contacts' or sums 'all donations' is quietly wrong once a tenant grows past 1k rows. In one case a recipient preview showed exactly 1000 and the real send was capped too, because both went through the same unpaginated query. Write one fetch_all_paginated helper that loops .range(start, start+999) until a page comes back short, and use it for every count, aggregate, set-difference and segment query. A count that lands on exactly 1000 is the giveaway.
