CHANNEL_ERROR error: mismatch between server and client bindings for postgres changes

Having issues with Realtime postgres_changes - "mismatch between server and client bindings"

I'm getting this error when subscribing to a notifications table:
CHANNEL_ERROR error: mismatch between server and client bindings for postgres changes

Code:

const channel = supabase
  .channel(

const channel = supabase
  .channel(

const channel = supabase
  .channel(

const channel = supabase
  .channel(

notifications:${uid}

)
  .on('postgres_changes', { event: '*', schema: 'public', table: 'notifications' }, (payload) => {
    console.log('event:', payload);
  })
  .subscribe((status, err) => {
    console.log(status, err?.message);
  });

)
  .on('postgres_changes', { event: '*', schema: 'public', table: 'notifications' }, (payload) => {
    console.log('event:', payload);
  })
  .subscribe((status, err) => {
    console.log(status, err?.message);
  });

)
  .on('postgres_changes', { event: '*', schema: 'public', table: 'notifications' }, (payload) => {
    console.log('event:', payload);
  })
  .subscribe((status, err) => {
    console.log(status, err?.message);
  });

)
  .on('postgres_changes', { event: '*', schema: 'public', table: 'notifications' }, (payload) => {
    console.log('event:', payload);
  })
  .subscribe((status, err) => {
    console.log(status, err?.message);
  });

What I've verified:
Table is in the supabase_realtime publication (confirmed via SELECT * FROM pg_publication_tables)
Tried dropping and re-adding table to publication
Toggled Realtime on/off in dashboard
RLS is enabled with proper policies
Other tables (goals, tasks, comments) work fine with identical pattern
The weird thing is websocket messages briefly show "Subscribed to PostgreSQL" with status "ok", then immediately get a phx_close event. Using hosted Supabase, supabase-js latest. Any ideas?

garyaustin•12/4/25, 3:15 AM

Maybe something here will help... https://github.com/orgs/supabase/discussions/39441

Note support has been answering these with use broadcast from database instead of database_changes in some cases...

NullOP•12/4/25, 4:04 AM

Thanks Gary. Does that suggest this is not a problem with my code, but a bug with supabase?

garyaustin•12/4/25, 4:06 AM

I have no idea. I'm just linking a post I was on that did not have a clear solution for one case and for another it was code format you don't have.

But also saying not sure if support will track it down or just tell you to use broadcast. You could also file an issue in supabase/realtime.

I'm skeptical another user here will have info for you.

garyaustin•12/4/25, 4:07 AM

Realtime postgres_changes is working in general though or there would be more issues.

NullOP•12/5/25, 1:20 AM

rgr that. I switched to broadcast and I'm unblocked. Thanks

garyaustin•12/5/25, 1:21 AM

It is the right move long term.

CHANNEL_ERROR error: mismatch between server and client bindings for postgres changes

Similar Threads

Similar Threads

Similar Threads