Re: [BUGS] 6.5.2 BUG: Rolling back after dropping a table causes dangling relationships.

From: Lincoln Yeoh <lylyeoh(at)mecomb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: [BUGS] 6.5.2 BUG: Rolling back after dropping a table causes dangling relationships.
Date: 1999-10-09 04:12:43
Message-ID: 3.0.5.32.19991009121243.00889ab0@pop.mecomb.po.my
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

At 10:04 AM 08-10-1999 -0400, Tom Lane wrote:
>Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> writes:
>> If you drop a table in a transaction and do a rollback, the table is "half
>> dropped", the table is gone but you cannot create a new table with the same
>> name, nor can you drop it again.
>
>Yes, this is a known problem that's rather difficult to fix.
>You can't undo a file removal :-(

I'm not really concerned about undoing/rolling back of a drop table. I'm
not surprised if "drop table" can't be rolled back.

The problem is that it is NOT _completely_ dropped, and you cannot recreate
a new table with the same name nor use the old one. It's in a zombie state.

Cheerio,

Link.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message EMOTO Masahiko 1999-10-09 06:20:03 BUG REPORT
Previous Message Bruce Momjian 1999-10-09 01:30:47 Re: [BUGS] 6.5.2 broken on alpha/Tru64 Unix 4.0d/cc