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

Re: BUG #5621: Insufficient locking of dependent objects

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Caleb Welton <cwelton(at)greenplum(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5621: Insufficient locking of dependent objects
Date: 2010-08-17 21:28:23
Message-ID: AANLkTimJyzndiM+YTJTf4dPMc5OdwT8R1z9EjFoukk0H@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Tue, Aug 17, 2010 at 2:15 PM, Caleb Welton <cwelton(at)greenplum(dot)com> wrote:
> There is a general class of concurrency bugs related to insufficient
> locking
> of dependent objects.  This can occur with just about any inter-object
> dependency that exists in the system:
>
>  Creating a table while dropping the schema it is in
>  Creating a table while dropping a type it depends on
>  Creating a function while dropping the language
>  Creating an aggregate while dropping the transition function.
>  Etc.

More specifically, I think the bug is that we don't really do much
locking on database objects other than tables.  This would be good to
fix, but probably we'd need to start by coming up with a coherent
overall plan.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2010-08-17 21:32:41
Subject: Re: BUG #5622: Query failed: server closed the connection unexpectedly
Previous:From: Thue Janus KristensenDate: 2010-08-17 21:26:54
Subject: BUG #5622: Query failed: server closed the connection unexpectedly

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