Re: patch: Add a separate TRUNCATE permission - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: patch: Add a separate TRUNCATE permission
Date
Msg-id 20080729110844.GL16005@tamriel.snowman.net
Whole thread Raw
In response to Re: patch: Add a separate TRUNCATE permission  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: patch: Add a separate TRUNCATE permission  (Peter Eisentraut <peter_e@gmx.net>)
Re: patch: Add a separate TRUNCATE permission  ("Robert Haas" <robertmhaas@gmail.com>)
List pgsql-hackers
* Peter Eisentraut (peter_e@gmx.net) wrote:
> Am Sunday, 27. July 2008 schrieb Robert Haas:
> > Here's a patch implementing the TODO item "Add a separate TRUNCATE
> > permission".  Hopefully I found all the bits that needed to be
> > modified to make this work.
>
> Looks very good to me.

We've been through this before, I believe..  The concern is that it
chews up another bit in the acl structure, leaving not a huge number
left.  My suggested approach to fixing this was to split the "grantable"
bits up from the regular usage bits.  That's, unfortunately, a
non-trivial amount of work, however.

Perhaps just having a plan for how we would increase the number of
available bits would be enough to go ahead and add this option though?
I'd certainly like to see a truncate permission, I wrote a patch for it
myself back in January of 2006.  That thread starts here:

http://archives.postgresql.org/pgsql-patches/2006-01/msg00028.php

I think someone else submitted a patch for it last year too, actually.Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: [WIP] patch - Collation at database level
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Python 2.5 vs the buildfarm