Re: Allow database owners to CREATE EVENT TRIGGER

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Steve Chavez <steve(at)supabase(dot)io>
Cc: Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow database owners to CREATE EVENT TRIGGER
Date: 2025-03-05 14:58:26
Message-ID: CAKFQuwbgjvupHPFjdGVz-T2miawVP=W3FN=KQdPvTSNtAbP-0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 5, 2025 at 7:55 AM Steve Chavez <steve(at)supabase(dot)io> wrote:

> How about requiring explicit non-superuser execution for the database
> owner evtrig? It would be like:
>
> CREATE EVENT TRIGGER name ... FOR NOSUPERUSER;
>

This is more what I was thinking - which works for a boolean. The ability
to have an exclusion list would make sense, or maybe just a predefined role
pg_bypass_eventtriggers.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-03-05 15:12:14 Re: Non-text mode for pg_dumpall
Previous Message Sami Imseih 2025-03-05 14:57:28 Re: should num_custom_plans be reset after plan invalidation?