SupaMigrateStart migration

Error reference

Supabase & Postgres errors

The errors that actually show up when you migrate a database — what each one means, why it happens, and the exact SQL that fixes it.

auth

permission denied for schema public"permission denied for schema public" (SQLSTATE 42501) means the current role lacks USAGE or CREATE on the schema it is touching. Since Postgres 15 the PUBLIC role no longer gets CREATE on schema public by default, so roles that used to work now fail on CREATE TABLE. Fix it by granting the missing privilege to the role, or by running the DDL as the schema owner or the postgres superuser.

connection

data

insert or update on table "orders" violates foreign key constraint "orders_user_id_fkey"Postgres raises SQLSTATE 23503 when a row you insert references a parent key that does not exist in the referenced table. During a migration this almost always means child rows (orders) were loaded before their parents (users), or the parent row failed to insert. Load tables in foreign-key dependency order, defer the constraints inside one transaction, or add the FK after the data is in.

schema

storage

duplicate key value violates unique constraint "buckets_pkey"This means you tried to insert a row into storage.buckets whose primary key (the bucket id) already exists. During a migration it usually happens because the destination project already has the default buckets, or the migration re-ran and tried to create the same bucket twice.