supabase / supabase / 20038891176 / 1 – studio-tests

74%

master: 74%

push

github

fix(export all rows): use cursor pagination if possible (#40536)

Exporting all rows (in CSV, SQL, or JSON format) currently uses offset pagination, which can cause performance problems if the table is large. There is also a correctness problem if the table is being actively updated as the export happens, because the relative row offsets could shift between queries.

Now that composite filters are available in postgres-meta, we can change to using cursor pagination on the primary key (or any non-null unique keys) wherever possible. Where this is not possible, the user will be shown a confirmation dialog explaining the possible performance impact.

---------

Co-authored-by: Ali Waseem <waseema393@gmail.com>
Co-authored-by: Joshen Lim <joshenlimek@gmail.com>

476 of 566 branches covered (84.1%)

Branch coverage included in aggregate %.

1992 of 3033 relevant lines covered (65.68%)

132.51 hits per line