Disabling "Realtime" for a single table disables realtime for the entire database about supabase

[sagitarious12]

Here is all of the postgres commands that I used to setup a test environment to verify the issue in a fresh environment with no other tables besides the ones created in this script:

CREATE SCHEMA "order";

GRANT USAGE ON SCHEMA "order" TO anon;

create table
  "order".infinity_rips (
    id bigint generated by default as identity,
    height bigint null,
    constraint infinity_rips_pkey primary key (id),
  ) tablespace pg_default;

GRANT ALL ON TABLE "order".infinity_rips TO anon;

ALTER TABLE "order".infinity_rips ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Enable read access for all users" ON "order"."infinity_rips"
AS PERMISSIVE FOR ALL
TO anon
USING (true);

create table
  "order".header_designs (
    id bigint generated by default as identity,
    design_name text null,
    constraint header_designs_pkey primary key (id),
  ) tablespace pg_default;
  
GRANT ALL ON TABLE "order".header_designs TO anon;

ALTER TABLE "order".header_designs ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Enable read access for all users" ON "order"."header_designs"
AS PERMISSIVE FOR ALL
TO anon
USING (true);

INSERT INTO "order".infinity_rips 
  (height) 
VALUES 
  (2);

INSERT INTO "order".header_designs
  (design_name)
values
  ('some design');

[GaryAustin1]

This is discussed a bit more here: https://github.com/orgs/supabase/discussions/26896
I suspect this is being an issue with making changes while the subscription is running on two tables from the client and getting errors on one impacting the other as they are in the same channel.