| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | Steve Chavez <steve(at)supabase(dot)io>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow database owners to CREATE EVENT TRIGGER |
| Date: | 2025-03-05 13:54:55 |
| Message-ID: | CAKFQuwZaW21Td4gK92wNYhFo4j7mxAA3XZjptzgcA3V=9xwZYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday, March 5, 2025, Aleksander Alekseev <aleksander(at)timescale(dot)com>
wrote:
>
> > Unlike superuser event triggers, which execute functions for every role,
> database owner event triggers are only executed for non-superusers.
>
All this doesn't strike me as a great UI.
>
Yeah. Seems better to make “execute_for” an attribute of the trigger and
allow both superusers and non-superusers to create them. Then enforce that
non-superusers must specify the more limited value.
Though it would seem nice to be able to exclude the pseudo-admin roles
these service providers create as well.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2025-03-05 14:03:46 | Re: Allow LISTEN on patterns |
| Previous Message | Jacob Champion | 2025-03-05 13:47:08 | Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible |