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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fred Habash <fmhabash(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Allowing John to Drop Triggers On Chad's Tables
Date: 2021-03-15 21:10:24
Message-ID: 3076346.1615842624@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Fred Habash <fmhabash(at)gmail(dot)com> writes:
> Based on my research, There are the options I have identified to allow user
> 'John' to drop a trigger on a table owner by 'Chad' ..

I guess the big-picture question is why do you think you need that?

The separate TRIGGER permission is something we consider obsolescent.
It's difficult to make use of it in any way that isn't tantamount to
giving John the ability to execute arbitrary code as Chad (the next
time Chad does anything with his table). So while a case could be
made that granting TRIGGER should include the right to alter or drop
existing triggers, it's unlikely that anyone will want to expend effort
in that direction.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2021-03-15 22:06:21 Re: sql3types.h does not include "BigInt"
Previous Message Niko Ware 2021-03-15 19:34:16 sql3types.h does not include "BigInt"