| From: | newtglobal postgresql_contributors <postgresql_contributors(at)newtglobalcorp(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Nikolay Samokhvalov <nikolay(at)samokhvalov(dot)com> |
| Subject: | Re: pg_dump, pg_dumpall, pg_restore: Add --no-policies option |
| Date: | 2025-03-13 06:52:35 |
| Message-ID: | 174184875546.294107.9656924571663274690.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The following review has been posted through the commitfest application:
make installcheck-world: not tested
Implements feature: not tested
Spec compliant: not tested
Documentation: not tested
Hi,
Tested this patch with `--no-policies` option works as expected by ensuring that policy definitions are not included in database backups. Successfully tested using `pg_dump`, `pg_dumpall`, and `pg_restore`, confirming that policies are excluded upon restoration. The `admin_full_access` policy was correctly applied, granting full access to the `admin` role for the `users` table. Additionally, the `read_only_access` policy was verified to restrict the `readonly` role to only performing `SELECT` operations.
Regards,
Newt Global PostgreSQL Contributors
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2025-03-13 06:52:48 | Re: Test to dump and restore objects left behind by regression |
| Previous Message | newtglobal postgresql_contributors | 2025-03-13 06:51:40 | Re: Add XMLNamespaces to XMLElement |