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

From Tom Lane
Subject Re: Regarding TODO item "%Add a separate TRUNCATE permission"
Date
Msg-id 19735.1146074066@sss.pgh.pa.us
Whole thread Raw
In response to Re: Regarding TODO item "%Add a separate TRUNCATE permission"  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Regarding TODO item "%Add a separate TRUNCATE permission"  (Stephen Frost <sfrost@snowman.net>)
Re: Regarding TODO item "%Add a separate TRUNCATE permission"  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Regarding TODO item "%Add a separate TRUNCATE  (Gevik Babakhani <pgdev@xs4all.nl>)
List pgsql-hackers
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.

In any case, I don't feel it necessary to panic about running out of
permission bits when the space is only 75% used... with a little care
it'll last us a long time yet, and I'm not eager to pay any performance
price whatsoever just so we can invent the Joe Hacker Memorial Privilege
Bit.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Regarding TODO item "%Add a separate TRUNCATE
Next
From: Stephen Frost
Date:
Subject: Re: Regarding TODO item "%Add a separate TRUNCATE