Subject: Re: [COMMITTERS] pgsql: Fix LOCK TABLE to eliminate the
	race condition that could make it
From: Simon Riggs <simon@2ndQuadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
In-Reply-To: <200906021833.n52IXLx26557@momjian.us>
References: <200906021833.n52IXLx26557@momjian.us>
Content-Type: text/plain
Date: Thu, 04 Jun 2009 09:38:12 +0100
Message-Id: <1244104692.23910.139.camel@ebony.2ndQuadrant>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


On Tue, 2009-06-02 at 14:33 -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Simon Riggs <simon@2ndquadrant.com> writes:
> > > If we're going to require cascaded permissions like this, would it make
> > > sense to make GRANT cascade down the inheritance tree also? 
> > 
> > That's been discussed before.  I forget whether we decided it was a good
> > idea or not, but in any case it looks like a new feature not a bug fix.
> 
> Is this a TODO?

Yes.

Whatever was discussed before was prior to the changes to make TRUNCATE
and LOCK TABLE cascade. The cascading will fail without appropriate
permissions, so GRANT should work that way also, now.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support