Re: ROLLBACK of DROP TABLE leaves database in inconsistent state - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ROLLBACK of DROP TABLE leaves database in inconsistent state
Date
Msg-id 12238.957651679@sss.pgh.pa.us
Whole thread Raw
In response to ROLLBACK of DROP TABLE leaves database in inconsistent state  ("Oliver Elphick" <olly@lfix.co.uk>)
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: You're on SecurityFocus.com for the cleartext passwords.
Next
From: "Hiroshi Inoue"
Date:
Subject: RE: pg_group_name_index corrupt?