FG
๐Ÿ’ป Software๐Ÿ—„๏ธ Databases

Realtime Row Level security broken for database-wide subscriptions on PG12

Freshabout 4 years ago
Mar 14, 20260 views
Confidence Score86%
86%

Problem

Bug report Describe the bug Affects - PG12 - PG14 (although these will only be new use-cases, so nobody should be experiencing the bug) Unaffected - PG13 users. If you are experiencing problems with PG13, it is probably because your Policies are not allowing access (whereas previously Policies weren't applied). This is intended behaviour - your database security is working properly Description We're discovered an issue as a result of our Row-Level Security Realtime updates for that affects any database-wide publications. (eg `CREATE PUBLICATION supabase_realtime FOR ALL TABLES;`) To Reproduce Realtime subscription may have stopped you are on PG12 and you have a Publication in your database set up like <img width="1467" alt="Screenshot 2021-12-01 at 7 49 05 PM" src="https://user-images.githubusercontent.com/10214025/144230037-9539750e-7092-40f3-9487-f3eeac582ed9.png"> Workaround Disable the `FULL` publication (red) and enable each table individually (green) <img width="1467" alt="Screenshot 2021-12-01 at 7 50 51 PM" src="https://user-images.githubusercontent.com/10214025/144229745-0747d54e-dc4e-4a5a-a286-a63e0cfdfd0b.png">

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
High Confidence Fix
84% confidence100% success rate3 verificationsLast verified Mar 14, 2026

Solution: Realtime Row Level security broken for database-wide subscriptions on PG12

Low Risk

It looks like a permission issue is blocking `pg_dump` on our side: [code block] Granting privileges to the table using the online SQL editor solved the issue: [code block]

84

Trust Score

3 verifications

100% success
  1. 1

    It looks like a permission issue is blocking `pg_dump` on our side:

    It looks like a permission issue is blocking `pg_dump` on our side:

  2. 2

    Granting privileges to the table using the online SQL editor solved the issue:

    Granting privileges to the table using the online SQL editor solved the issue:

Validation

Resolved in supabase/supabase GitHub issue #4201. Community reactions: 2 upvotes.

Verification Summary

Worked: 3
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

supabasepostgresqlbackendbug