Supabase CLI migration failure cleanup behavior

Supabase CLI migration error: relation already exists after failed upgrade

26K reputation · 07 Apr 2022, 03:43 UTC

87K views0

After a Supabase migration fails with the error “relation already exists”, the CLI records the last good version in supabase_migrations but it is unclear whether it automatically removes any temporary database objects that were created during the failed run.

The documentation does not guarantee cleanup of orphaned indexes, constraints or other schema artifacts, leaving open the possibility of schema drift if such objects remain.

What is the expected CLI behavior regarding cleanup after a failure, and is manual inspection or removal required to ensure a clean state?

3,887 following

Keep exploring this topic

Supabase CLI and GitHub Actions: Consistent Schema Migration Handling

Ensuring consistent schema migrations between Supabase CLI local development and GitHub Actions CI pipelines.

Supabase migration CLI: Does a single-transaction apply block reads during large DDL?

Investigating whether the Supabase migration CLI’s single‑transaction apply blocks reads during large DDL changes, and exploring options for zero‑downtime schema updates.

SQLite state file may be partially written after interrupted Reflex 0.5.0 migration

Explains the risk of a partially written SQLite state file after an interrupted Reflex 0.5.0 migration and asks about detection, fallback, and future transactional improvements.

Backup creation limit for Quasar CLI upgrade safety in v2.x

Discusses whether Quasar CLI should automatically back up package.json and lockfiles before upgrades to enable safe recovery from a failed update.

Supabase CLI migration error: relation already exists after failed upgrade

0 answers

Your perspective belongs here.

0 question comments