Supabase Releases Stability

Table subscribed via Realtime but absent from the supabase_realtime publication

Part of the Realtime & cost check · fix arrives as a pull request

What it is

Application code subscribes to postgres_changes on a table that no migration has added to the supabase_realtime publication.

Why it matters

The subscription connects successfully and receives nothing. There is no error on either side, so the feature simply does not work and looks like a client bug.

How to fix it

Add the table to the publication in a migration: ALTER PUBLICATION supabase_realtime ADD TABLE public.your_table;. Keeping it in a migration means new environments get it automatically.

Also in Realtime & cost

Unfiltered Realtime subscription broadcasts every mutation SupabaseRealtime & cost Realtime channel never unsubscribed — connection leak SupabaseRealtime & cost Polling loop queries Supabase on a short interval — use Realtime instead SupabaseRealtime & cost select('*') fetches every column — unnecessary egress SupabaseRealtime & cost

Run them all on your app

Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.

Guard my app · Free → View pricing