DETACH RLS POLICY - Amazon Redshift
SyntaxParametersUsage notesExamples

Amazon Redshift will no longer support the creation of new Python UDFs starting November 1, 2025. If you would like to use Python UDFs, create the UDFs prior to that date. Existing Python UDFs will continue to function as normal. For more information, see the blog post .

DETACH RLS POLICY

Detach a row-level security policy on a table from one or more users or roles.

Superusers and users or roles that have the sys:secadmin role can detach a policy.

Syntax

DETACH RLS POLICY
{
  policy_name ON [TABLE] table_name [, ...]
  | database_name.policy_name ON [TABLE] database_name.schema_name.table_name [, ...]
}
FROM { user_name | ROLE role_name | PUBLIC } [, ...];

Parameters

policy_name

The name of the policy.

database_name

The name of the database where the policy and the relation are created. The policy and the relation needs to be on the same database. The database can be the connected database or a database that supports Amazon Redshift federated permissions.

schema_name

The name of the schema the relation belongs to.

table_name

The relation that the row-level security policy is attached to.

FROM { user_name | ROLE role_name | PUBLIC} [, ...]

Specifies whether the policy is detached from one or more specified users or roles.

For the usage of DETACH RLS POLICY on Amazon Redshift Federated Permissions Catalog, see Managing access control with Amazon Redshift federated permissions.

Usage notes

When working with the DETACH RLS POLICY statement, observe the following:

  • You can detach a policy from a relation, user, role, or public.

Examples

The following example detaches a policy on a table from a role.

DETACH RLS POLICY policy_concerts ON tickit_category_redshift FROM ROLE analyst, ROLE dbadmin;