Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] column-level update privs + lock table

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] column-level update privs + lock table
Date: 2010-11-30 16:25:19
Message-ID: (view raw or whole thread)
Lists: pgsql-generalpgsql-hackers
On Tue, Nov 30, 2010 at 9:07 AM, Josh Kupershmidt <schmiddy(at)gmail(dot)com> wrote:
> On Mon, Nov 29, 2010 at 10:06 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Mon, Nov 29, 2010 at 9:37 PM, Josh Kupershmidt <schmiddy(at)gmail(dot)com> wrote:
>>> I actually hadn't thought of that, for some reason.
>>> We used to similarly recommend that people handle TRUNCATE privileges
>>> with a security definer function. That doesn't mean GRANT TRUNCATE
>>> wasn't a sweet addition to 8.4.
>> Hmm, glad you like it (I wrote that).  I'm just asking how far we
>> should go before we decide we catering to use cases that are too
>> narrow to warrant an extension of the permissions system.
> I am slightly opposed to adding GRANTs for LOCK TABLE, ANALYZE,
> VACUUM, etc. The GRANT help page is long enough already, and I doubt
> many users would use them, even though I might use GRANT LOCK TABLE
> myself.

You'd really probably want GRANT LOCK TABLE (SHARE), GRANT LOCK TABLE

It'd be sort of cool, but it doesn't seem worth the complexity.

Robert Haas
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-11-30 16:27:04
Subject: Re: crash-safe visibility map, take three
Previous:From: Robert HaasDate: 2010-11-30 16:22:03
Subject: Re: crash-safe visibility map, take three

pgsql-general by date

Next:From: A JDate: 2010-11-30 16:58:58
Subject: Extension for file management under postgres
Previous:From: Wappler, RobertDate: 2010-11-30 16:21:00
Subject: How to indicate failure of a shell script to pgagent

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group