Subject: Re: [COMMITTERS] pgsql: Fix LOCK TABLE to eliminate the race
	condition that could make it
From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
In-Reply-To: <9820.1242162624@sss.pgh.pa.us>
References: <20090512164332.BFC1575407D@cvs.postgresql.org>
	<1242161438.3843.334.camel@ebony.2ndQuadrant>
	<9820.1242162624@sss.pgh.pa.us>
Content-Type: text/plain
Date: Tue, 12 May 2009 22:15:26 +0100
Message-Id: <1242162926.3843.339.camel@ebony.2ndQuadrant>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


On Tue, 2009-05-12 at 17:10 -0400, 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.

Agreed. I was just trying to think ahead to the implications and
difficulties of the LOCK and TRUNCATE changes and see if anything else
important emerged.

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