Re: Big 7.1 open items - Mailing list pgsql-hackers

From Oliver Elphick
Subject Re: Big 7.1 open items
Date
Msg-id 200006141313.e5EDD9O14271@linda.lfix.co.uk
Whole thread Raw
In response to Re: Big 7.1 open items  (Peter Eisentraut <e99re41@DoCS.UU.SE>)
Responses Re: Big 7.1 open items  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>On Tue, 13 Jun 2000, Bruce Momjian wrote: > >> Here is the list I have gotten of open 7.1 items:

Rolling back a transaction after dropping a table creates a corrupted
database.  (Yes, I know it warns you not to do that, but users are
fallible and sometimes just plain stupid.)  Although the system catalog
entries are rolled back, the file on disk is permanently destroyed.

I suggest that DROP TABLE in a transaction should not be allowed.



-- 
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47  6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
========================================   "I beseech you therefore, brethren, by the mercies of      God, that ye
presentyour bodies a living sacrifice,      holy, acceptable unto God, which is your reasonable      service."
Romans12:1 
 




pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Back online
Next
From: "Dan Wilson"
Date:
Subject: Re: Modifying NOT NULL Constraint