Realtime does not work for tables with User-defined fields

[kausko]

Bug report

Describe the bug

One of my tables in the supabase_realtime publication has a column of user-defined type/enum. I'm unable to subscribe to changes in this table, but other tables in the realtime publication are working. Removing this column fixes this issue.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Create an enum/user-defined type

DO $$ BEGIN
  CREATE TYPE "level" AS ENUM (
    'OWNER',
    'GUEST'
  );
EXCEPTION
  WHEN duplicate_object THEN null;
END $$;

2. Create a table with a column of this type

CREATE TABLE IF NOT EXISTS "users" (
  id bigint GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
  access "level" DEFAULT 'GUEST' NOT NULL,
);

3. Add table to realtime publication

BEGIN; 
  DROP publication IF EXISTS supabase_realtime; 
  CREATE publication supabase_realtime;  
COMMIT;
ALTER publication supabase_realtime ADD TABLE users;

4. Subscribe to table(s)

client
.from("*")
.on("*", console.log)
.subscribe()

5. Wait for changes

Expected behavior

To receive payloads with updated data

System information

• OS: Windows
• Browser (if applies): Edge 96.0.1054.62 (Official build) (64-bit)
• Version of supabase-js: ^1.28.5
• Version of Node.js: 14.17.5

Additional context

Possibly related to #203 and #207?

[w3b6x9]

@kausko this is a known issue that we're currently dealing with. Realtime RLS, which is what all Supabase projects are currently using, rely on wal2json to function and we need to upgrade it v2.4. We'll be rolling out the upgrade to all Supabase projects in the next week or so.

We were going to deal with it using supabase/walrus#32 but then discovered that it's already been fixed upstream eulerto/wal2json#224.

In the meantime, you can define the type without quotation marks (i.e. "level" -> level) and it should work just fine.

If you're using a Supase project you can email support@supabase.io with your project ref and we can manually upgrade your db wal2json version to v2.4.

[kausko]

Thank you for getting back to me so quickly @w3b6x9!

Redefining the type without the quotation marks worked perfectly, so I'm closing this issue.

I really appreciate your offer for a manual upgrade, but I'll stick to your solution for now. Thanks again!