Permissions failures on subscriber cause replication conflicts
criticalsecurityUpdated Feb 26, 2026
Technologies:
How to detect:
Logical replication operations run with the privileges of the subscription owner role. If the owner lacks permissions on target tables or if row-level security policies are enabled that reject operations, replication will fail with conflicts and stop.
Recommended action:
Ensure subscription owner role has necessary permissions (INSERT, UPDATE, DELETE, TRUNCATE) on all target tables. Review row-level security policies on subscriber tables - they will be enforced for replication operations and can cause failures. Check subscriber server logs for permission-related errors. Grant appropriate privileges or adjust RLS policies to allow replication.