Re: ROLLBACK of DROP TABLE leaves database in inconsistent state

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ROLLBACK of DROP TABLE leaves database in inconsistent state
Date: 2000-05-06 22:21:19
Message-ID: 12238.957651679@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

This is news?

> junk=# drop table aaa;
> NOTICE: Caution: DROP TABLE cannot be rolled back, so don't abort now
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> DROP
> junk=# rollback;
> ROLLBACK

What did you think the NOTICE was trying to tell you? (I wanted to
make it a hard ERROR, but was shot down.)

This will be fixed eventually, but until something is done to decouple
filenames from relation names it can't be fixed properly. Consider
BEGIN; DROP TABLE foo; CREATE TABLE foo ...; ABORT. There are plans
in the pipeline to do that, and we'll fix it when that happens.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-05-06 23:50:16 RE: pg_group_name_index corrupt?
Previous Message Tom Lane 2000-05-06 22:12:54 Re: You're on SecurityFocus.com for the cleartext passwords.