Re: Allowing John to Drop Triggers On Chad's Tables

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Fred Habash <fmhabash(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Allowing John to Drop Triggers On Chad's Tables
Date: 2021-03-15 19:33:39
Message-ID: CAKFQuwZhrXfWh1Byt4KAU7s8d+AJPZp-ycsooRFAvQ1sog+JwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Mar 15, 2021 at 12:20 PM Fred Habash <fmhabash(at)gmail(dot)com> wrote:

> If there is a 'grant trigger' why is there not a 'grant drop trigger'?
>
>
Because creating a trigger from scratch doesn't let you affect other
triggers that you may not own (at least not directly). If drop permissions
were grantable the user could drop any trigger attached to said table. The
missing feature here is that triggers should probably have their own
ownership separate from a trigger and a trigger can only be attached to a
table where the trigger owner has trigger permissions. But the trigger
owner can always drop their owned triggers.

> Any other options since Chad has one table to allow John to drop triggers
> on?
>
>
Option 3 is the one that is expected to be used here. Well, aside from the
"John the person asks Chad the person to drop the trigger".

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Niko Ware 2021-03-15 19:34:16 sql3types.h does not include "BigInt"
Previous Message Fred Habash 2021-03-15 19:20:39 Allowing John to Drop Triggers On Chad's Tables