After updating to 2.15.0, postgres subscriptions with eq filter fail

[twhittock-disguise]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

After updating to 2.15.0 (from 2.11.15) via the updated supabase-js dependency, our realtime subscriptions stopped working.

Our subscriptions are made like this:

    messagesSubscription.value = supabaseClient
      .channel(`table:session_id=eq.${id.value}`)
      .on(
        'postgres_changes',
        {
          event: '*',
          schema: 'schema',
          table: 'table',
          filter: `session_id=eq.${id.value}`,
        },

Postgres logs are spammed with Invalid column for filter session_id messages.

To Reproduce

Make a subscription like the above in the new version.

Expected behavior

The subscription should either succeed or a clear upgrade path needs to be provided.

[filipecabaco]

@twhittock-disguise could you open a support ticket so I can check the logs and schema of your project?

This is related to the pull query used by postgres_changes ( https://github.com/supabase/realtime/blob/9aed8393e7214bbfb2c5a81a2711f5bcd1124626/lib/realtime/tenants/repo/migrations/20230227211149_update_subscription_check_filters_for_in_filter_non_text_types.ex#L40 ) so I need some extra information to properly understand what could be happening

[twhittock-disguise]

I raised support request SU-233594

[UngererFabien]

Hello! Any news on this? Made the same update from 2.11 to 2.15 and subscription is good but I'm not getting any change events.

[UngererFabien]

Hello @twhittock-disguise I had the same issue. Calling await supabaseClient.realtime.setAuth() before subscription solved the problem for me.

It seems like there is a delay from catching the JWT that create the issue when using RLS.

You can find the source for setAuth here: https://github.com/supabase/realtime-js/blob/master/src/RealtimeClient.ts

[UngererFabien]

I sent a message to the support. And they told me to migrate to Broadcast, linking to this blog post: https://supabase.com/blog/realtime-broadcast-from-database

And funny enough in there you can find the same call to supabaseClient.realtime.setAuth() stated as "Needed for Realtime Authorization".

So at this point it looks intended and might just need a doc update.

[ChrisChinchilla]

@twhittock-disguise and @UngererFabien As far as I can see, the docs should now be up to date, but let me know if you see anything that isn't.

[twhittock-disguise]

@ChrisChinchilla I'm not sure what you mean - the postgres changes are still documented and still work in older versions and are still broken in newer versions, what should I have done differently according to the docs? What changed in the docs?

[filipecabaco]

Hey sorry for the delay in the response.

The issue might be related with the different versions of supabase-js as newer versions do not require await supabaseClient.realtime.setAuth() but older versions do.

I will change the docs to reflect the need of await supabaseClient.realtime.setAuth() as most users will be running older versions.

So, TLDR:

• since 2.58.0 we no longer need this call
• due to the usage pattern of supabase-js I'm going to update the docs to include the setAuth() approach