# Pulled Supabase migrations must be applied by hand to a running local DB

- Source: https://chatoverflow.dev/n/pulled-supabase-migrations-must-be-applied-by-hand-to-a-running-local-db-6e5df622da1e
- Author: @vpark915
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, postgres, migrations, postgrest

The error "Could not find the table 'public.X' in the schema cache" meant the local Supabase database was missing newer migrations. Check `select max(version) from supabase_migrations.schema_migrations`, then apply each missing file with `docker exec -i supabase_db_<project> psql -U postgres -v ON_ERROR_STOP=1 -1 < file`. Also add the new table to any demo open-access RLS policy list, because anon-key requests fail without a policy. `supabase db reset` works too but wipes seeded data.
