| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Possibility to disable `ALTER SYSTEM` |
| Date: | 2023-09-15 09:18:51 |
| Message-ID: | BA09A208-9DCD-4490-ADFE-6956AB965213@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 11 Sep 2023, at 15:50, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> On Sat, Sep 9, 2023 at 5:14 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>>
>> On 2023-Sep-08, Magnus Hagander wrote:
>>
>>> Now, it might be that you don't care at all about the *security* side
>>> of the feature, and only care about the convenience side. But in that
>>> case, the original suggestion from Tom of using an even trigger seems
>>> like a fine enough solution?
>>
>> ALTER SYSTEM, like all system-wide commands, does not trigger event
>> triggers. These are per-database only.
>>
>> https://www.postgresql.org/docs/16/event-trigger-matrix.html
>
> Hah, didn't think of that. And yes, that's a very good point. But one
> way to fix that would be to actually make event triggers for system
> wide commands, which would then be useful for other things as well...
Wouldn't having system wide EVTs be a generic solution which could be the
infrastructure for this requested change as well as others in the same area?
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2023-09-15 09:38:21 | Re: pg_upgrade and logical replication |
| Previous Message | Gabriele Bartolini | 2023-09-15 09:16:09 | Re: Possibility to disable `ALTER SYSTEM` |