| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | allow_system_table_mods and DROP RULE |
| Date: | 2019-12-18 08:56:42 |
| Message-ID: | ee9df1af-c0d8-7c82-5be7-39ce4e3b0a9d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
As a curious omission, DROP RULE does not check allow_system_table_mods.
Creating and renaming a rule does, and also creating, renaming, and
dropping a trigger does. The impact of this is probably nil in
practice, but for consistency we should probably add that. The patch is
pretty simple.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Disallow-dropping-rules-on-system-tables-by-default.patch | text/plain | 3.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-12-18 09:55:16 | Re: [Proposal] Level4 Warnings show many shadow vars |
| Previous Message | Juan José Santamaría Flecha | 2019-12-18 08:52:07 | Re: [PATCH] Windows port add support to BCryptGenRandom |