ALTER POLICY — change the definition of a row-level security policy
ALTER POLICYnameONtable_nameRENAME TOnew_nameALTER POLICYnameONtable_name[ TO {role_name| PUBLIC | CURRENT_ROLE | CURRENT_USER | SESSION_USER } [, ...] ] [ USING (using_expression) ] [ WITH CHECK (check_expression) ]
ALTER POLICY changes the definition of an existing row-level security policy. Note that ALTER POLICY only allows the set of roles to which the policy applies and the USING and WITH CHECK expressions to be modified. To change other properties of a policy, such as the command to which it applies or whether it is permissive or restrictive, the policy must be dropped and recreated.
To use ALTER POLICY, you must own the table that the policy applies to.
In the second form of ALTER POLICY, the role list, using_expression, and check_expression are replaced independently if specified. When one of those clauses is omitted, the corresponding part of the policy is unchanged.
nameThe name of an existing policy to alter.
table_nameThe name (optionally schema-qualified) of the table that the policy is on.
new_nameThe new name for the policy.
role_nameThe role(s) to which the policy applies. Multiple roles can be specified at one time. To apply the policy to all roles, use PUBLIC.
using_expressionThe USING expression for the policy. See CREATE POLICY for details.
check_expressionThe WITH CHECK expression for the policy. See CREATE POLICY for details.
ALTER POLICY is a PostgreSQL extension.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.