-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql,security: support row level security #73596
Comments
Hello, I am Blathers. I am here to help you get the issue triaged. It looks like you have not filled out the issue in the format of any of our templates. To best assist you, we advise you to use one of these templates. I was unable to automatically find someone to ping. If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
Thanks for this request! We hope to get to this in a future release, but don't have a definite timeline right now. |
Any update on timeline? |
Joining the topic as well |
Bumping this issue as it is currently inhibiting me from efficiency isolating tenant data without having to create separate schemas. RLS is a very nice feature of Postgres and it would be great if CockroachDB could implement it as well. |
For a system designed around multi-tenant workflows, it is astonishing to see this absence of row-level isolation. Combining it with AI, which assumes PostgreSQL compatibility (wire protocol, but the rest is mix of partially implemented features), only for the end user to hit into wall after wall. The day that PostgreSQL implements proper distribution, is the day that CRDB sales will drop. |
RLS is being actively worked on and we are targeting 25.2 (May) for a release. |
Support more fine-grained security control,such as row-level security. Different users/roles can view different rows of table.
An example is Rows Security Policies about PostgreSQL
MVP
Post-MVP
Epic CRDB-11724
Jira issue: CRDB-11657
The text was updated successfully, but these errors were encountered: