Re: Regarding TODO item "%Add a separate TRUNCATE permission" - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Regarding TODO item "%Add a separate TRUNCATE permission"
Date
Msg-id 200604261813.k3QIDvo26076@candle.pha.pa.us
Whole thread Raw
In response to Re: Regarding TODO item "%Add a separate TRUNCATE permission"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Regarding TODO item "%Add a separate TRUNCATE permission"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Stephen Frost <sfrost@snowman.net> writes:
> > we need
> > to redesign the permission system to allow for more permission bits
> > because otherwise we'll run out soon.
> 
> Only if we keep inventing separate privileges for things as specific
> as TRUNCATE.  I was just about to raise this point as a possible reason
> why not to invent a separate TRUNCATE bit.  (There are other problems,
> eg both 't' and 'T' letters are already taken.)
> 
> The question that really ought to be answered before doing any of this
> is why DELETE privilege shouldn't be sufficient to allow TRUNCATE.

TODO has:
* %Add a separate TRUNCATE permission  Currently only the owner can TRUNCATE a table because triggers are not  called,
andthe table is locked in exclusive mode.
 

--  Bruce Momjian   http://candle.pha.pa.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Regarding TODO item "%Add a separate TRUNCATE permission"
Next
From: Alvaro Herrera
Date:
Subject: Re: Regarding TODO item "%Add a separate TRUNCATE permission"