Can not access table migration on superuser role

[FredericoGauz]

Bug report

• [ x] I confirm this is a bug with Supabase, not with my own application.
• [x ] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

A clear and concise description of what the bug is.

When trying to access the migrations table I receive the following error (exact words vary depending on the command used at the time, this is from supabase link):

failed to fetch storage migration: ERROR: permission denied for table migrations (SQLSTATE 42501)

Same error will show up if I try to grant permissions either to only migrations table (or the storage schema) or all the tables via query:

GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA storage TO postgres;

ERROR: 42501: permission denied for table migrations

This error is not allowing me to create backups or to run supabase locally.

To Reproduce

Just run the query:

GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA storage TO postgres;

Expected behavior

The postgres role should have all migrations table (storage schema) permissions.

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: [e.g. 6.0.2]
• Version of Node.js: [e.g. 10.10.0]

Additional context

It's probably a problem with my user only, but I am not sure.

[olivercvetkovic]

i have the same issue

[alexkess101]

I'm also having this issue

[Hallidayo]

Hi, Are you trying to access the migrations when the project is created or migrations which are ran from the cli?

[FredericoGauz]

Hi, Are you trying to access the migrations when the project is created or migrations which are ran from the cli?

Hi, I first run this issue when trying to backup my db. Then when trying to run it locally using npx supabase link.

When trying to find out what the issue is I narrowed down to this permission issue when executing anywhere that would try to read this migration table from storage.

So, if I understood your question well, it would be from cli. Since the project already exists, if it helps, I could also point out the date it started because it was when my automated backups started to fail.

From the top of my head it was around 2 or 3 weeks ago, but I might be able to get a more accurate date.

Hope it helps!

[FredericoGauz]

Update: I couldn't pin point the exact date, but on 19th of September I was already this issue and for sure on the 8th of September I did not. Did anything related to this changed meanwhile?

[Hallidayo]

Just transferred over from the supabase repo as it seems like a cli issue?

[sweatybridge]

What's your project ref? We have to run a migration to patch it

[FredericoGauz]

Hi,

It is xxxxxxx could you let me know when it is done?

Thank you in advance!

[sweatybridge]

Ok I just realised you want to access storage.migrations table. This is no longer allowed as intended.

There is currently bug affecting read access to storage schema on pg15 projects.

[FredericoGauz]

Hi, I don't really need it. But whenever I try to to create a backup or run locally (using something like: npx supabase link I get this error. This was not the case about a month ago.

What looks like is that perhaps, for some reason, when I try to run these commands the supabase system is trying to access this specific table, when before is was not. (If it is the case that this table was always off limits).

And I am using pg_dump for running a backup.

[jmgunter]

I have the same issue. npx supabase link used to run fine locally, but recently started failing with: failed to fetch storage migration: ERROR: permission denied for table migrations (SQLSTATE 42501). Any solutions yet? I can't seem to apply any migrations now. Project ref = kmoznwlvipsaaiklyjuc

[sweatybridge]

I can confirm this is a bug on the platform side affecting some projects on pg15. While we work on a fix, you can run the following query manually from the dashboard to fix it.

grant pg_read_all_data to postgres

This should resolve the permission error from accessing storage.migrations table.