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

BUG #3833: Index remains when table is dropped

From: "Laurenz Albe" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3833: Index remains when table is dropped
Date: 2007-12-21 11:28:49
Message-ID: 200712211128.lBLBSnCJ014986@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      3833
Logged by:          Laurenz Albe
Email address:      laurenz(dot)albe(at)wien(dot)gv(dot)at
PostgreSQL version: 8.2.5
Operating system:   RedHat Enterprise Linux 3
Description:        Index remains when table is dropped
Details: 

Two concurrent sessions perform statements against one database. The
sessions are named s1 and s2 in this example.

s1=> CREATE TABLE x(i integer);

s2=> BEGIN;
s2=> CREATE UNIQUE INDEX x_pkey ON x(i);

s1=> DROP TABLE x;
(Session hangs)

s2=> COMMIT;

Now Session s1 will unblock and succeed in dropping the table. The index,
however, remains in pg_class, pg_depend, and pg_index.

"DROP INDEX x_pkey" will lead to an error like this:
ERROR:  could not open relation with OID 65615
The OID here is the one of the dropped table.

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2007-12-21 12:56:36
Subject: Re: BUG #3833: Index remains when table is dropped
Previous:From: Magnus HaganderDate: 2007-12-21 09:31:38
Subject: Re: BUG #3821: Wrong language at "Installation Notes"

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