ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Cloud & infrastructure · #supabase
Supabase migration CLI and transaction scope The Supabase CLI’s supabase migration apply runs all SQL statements in a single transaction by default. When a migration includes large DDL changes—such as adding an index to a table with millions of rows—this transaction can acquire an exclusive lock on the target table. The lock may prevent concurrent SELECTs, l
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 artifac
I run a low-traffic side project on Supabase's free tier. My understanding is that free-tier projects are automatically paused after a period of inactivity (roughly a week, historically), and the database stops responding until it is restored through the dashboard or API. Before I commit to a paid plan, I want to make sure I am diagnosing the right trade-off