ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Cloud & infrastructure · #supabase
Goal: achieve identical schema migration outcomes when running Supabase CLI locally via supabase start and in a CI pipeline that uses supabase db push against a temporary project. Constraints: the CLI does not automatically remove ephemeral Supabase projects created for CI, requiring manual cleanup to avoid quota limits, and the Docker images pulled by supab
When migrating data from an external PostgreSQL instance to a Supabase project using the postgres_fdw extension, the transfer of table rows does not automatically synchronize the state of sequence generators. In a zero-downtime migration strategy, data is pulled into the target Supabase instance while the source continues to accept writes. If the target sequ
Supabase leverages PostgREST to translate API requests into SQL queries. When retrieving large datasets using the limit and offset parameters, the underlying PostgreSQL engine must scan and discard rows prior to returning the requested page. As the offset value increases, there is a potential for linear degradation in query performance, leading to increased
PostgreSQL Logical Replication and Storage Supabase Realtime leverages the supabase_realtime publication and logical replication slots to stream database changes to clients via WebSockets. This architecture relies on the PostgreSQL Write Ahead Log (WAL) to track and broadcast INSERT , UPDATE , and DELETE events. Resource Constraints In environments with high
Our team runs a production Supabase project and wants alerting that is genuinely actionable. The platform exposes several distinct signal sources: query performance data built on pg_stat_statements, Auth audit events, connection pool saturation, and usage metrics for compute, bandwidth, and database size. Dashboard notifications cover some of this, while log
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
Recursive Policy Evaluation Supabase leverages PostgreSQL Row Level Security (RLS) to enforce data access via auth.uid() . In schemas where a table contains a self-referencing foreign key—such as a categories table with a parent_id column—policies often need to check the permissions of the parent record to determine access to the child record. Constraint and
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