Disconnect clients when updating RLS rules#3574
Merged
joshua-spacetime merged 4 commits intomasterfrom Nov 11, 2025
Merged
Conversation
11c4134 to
4245ae5
Compare
4245ae5 to
0041eca
Compare
0041eca to
8dab9b7
Compare
joshua-spacetime
approved these changes
Nov 11, 2025
Signed-off-by: joshua-spacetime <josh@clockworklabs.io>
Signed-off-by: joshua-spacetime <josh@clockworklabs.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
Disconnects clients when adding, removing, or updating RLS rules. Client are not disconnected if an auto-migration does not touch any RLS rules.
Subscriptions cache RLS rules. By disconnecting clients, we forcibly evict stale invalid RLS rules from the cache.
API and ABI breaking changes
Bug fix. Previously subscriptions would keep stale RLS rules in cache.
Expected complexity level and risk
1
Testing
spacetime subscribe