Max rows in API Settings doesn't work on local development

[danielvoelk]

Describe the bug

In my config.toml I'm settings the max rows:

max_rows = 1000000

But the value is not applied. It only returns 1000 rows.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Set max rows to a higher value than 1000
2. Fetch data from a table with more than 1000 rows
3. See that only 1000 rows will be returned

Expected behavior

I exptected to receive all rows, until a maximum of 1000000.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• OS: [e.g. macOS, Windows]
• Browser (if applies) [e.g. chrome, safari]
• Version of supabase-js: 2.39.2
• Version of Node.js: v18.17.0

Additional context

In my staging and production environment it works. Only the local development environment ignores the max_row configuration.

[krizzu]

Behind the hood, the max_row config is used in setting env variable PGRST_DB_MAX_ROWS, used to tell postgrest about the row limit. Having said that, once u set the value in config.yaml, you have to restart docker container (supabase stop && supabase start)