| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Fix LOCK TABLE to eliminate the race condition that could make it |
| Date: | 2009-05-12 21:15:26 |
| Message-ID: | 1242162926.3843.339.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, 2009-05-12 at 17:10 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Bmomjian | 2009-05-12 21:50:43 | pg-migrator - pg_migrator: Small cleanups. |
| Previous Message | Tom Lane | 2009-05-12 21:10:24 | Re: [COMMITTERS] pgsql: Fix LOCK TABLE to eliminate the race condition that could make it |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-05-12 21:20:14 | Re: Implementation of GROUPING SETS (T431: Extended grouping capabilities) |
| Previous Message | Tom Lane | 2009-05-12 21:10:24 | Re: [COMMITTERS] pgsql: Fix LOCK TABLE to eliminate the race condition that could make it |