Re: DROP TABLE vs inheritance

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: DROP TABLE vs inheritance
Date: 2009-05-12 18:10:08
Message-ID: 34d269d40905121110ye0a3350kb25ea330c3e26334@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 11, 2009 at 21:18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> However, he can do that anyway via ALTER TABLE, which
> will happily take out AccessExclusiveLock before it checks any
> permissions.  So I'm not seeing the point of risking unsafe behavior
> in LOCK TABLE.

I would rather fix ALTER TABLE to do something similar to test and
test-and-set... From a quick look TRUNCATE also seems to be prone to
this.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-05-12 20:16:02 Re: pg_migrator alpha 5 - truncates at 10 M rows
Previous Message Tom Lane 2009-05-12 16:43:32 pgsql: Fix LOCK TABLE to eliminate the race condition that could make it