Skip to content

Commit 4bd7a1a

Browse files
committed
docs: note JWT role grants after extension upgrades
1 parent d32d8bf commit 4bd7a1a

2 files changed

Lines changed: 4 additions & 0 deletions

File tree

docs/postgresql/quickstarts/postgres.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,8 @@ DROP EXTENSION IF EXISTS cloudsync CASCADE;
9999
CREATE EXTENSION cloudsync;
100100
```
101101

102+
If you use JWT authentication with PostgreSQL RLS, recheck the database grants for the role named in your JWT `role` claim after upgrading. Recreating the extension also recreates extension-owned objects such as `cloudsync_changes`, so grants on those objects may need to be reapplied. See [PostgreSQL Role Requirement](../reference/jwt-claims.md#postgresql-role-requirement).
103+
102104
---
103105

104106
## Step 3: Register Your Database in the CloudSync Dashboard

docs/postgresql/quickstarts/supabase-self-hosted.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,8 @@ DROP EXTENSION IF EXISTS cloudsync CASCADE;
100100
CREATE EXTENSION cloudsync;
101101
```
102102

103+
If you use JWT authentication with PostgreSQL RLS, recheck the database grants for the role named in your JWT `role` claim after upgrading. Recreating the extension also recreates extension-owned objects such as `cloudsync_changes`, so grants on those objects may need to be reapplied. See [PostgreSQL Role Requirement](../reference/jwt-claims.md#postgresql-role-requirement).
104+
103105
---
104106

105107
## Step 3: Register Your Database in the CloudSync Dashboard

0 commit comments

Comments
 (0)