From 8232f7fc9b3e59f55a74ca2a6c8e9ab6a898ff1b Mon Sep 17 00:00:00 2001 From: Yugo Nagata Date: Wed, 11 Jun 2025 16:59:09 +0900 Subject: [PATCH] Update README.md In addition to recreation, refresh may be used to apply changes to row-level security policies. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e4f0738..9b975c5 100644 --- a/README.md +++ b/README.md @@ -418,7 +418,7 @@ Even if we are able to acquire a lock, a concurrent transaction may have already ### Row Level Security -If some base tables have row level security policy, rows that are not visible to the materialized view's owner are excluded from the result. In addition, such rows are excluded as well when views are incrementally maintained. However, if a new policy is defined or policies are changed after the materialized view was created, the new policy will not be applied to the view contents. To apply the new policy, you need to recreate IMMV. +If some base tables have row level security policy, rows that are not visible to the materialized view's owner are excluded from the result. In addition, such rows are excluded as well when views are incrementally maintained. However, if a new policy is defined or policies are changed after the materialized view was created, the new policy will not be applied to the view contents. To apply the new policy, you need to refresh or recreate the IMMV. ### How to Disable or Enable Immediate Maintenance