From: | "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Big 7.1 open items |
Date: | 2000-06-14 13:13:09 |
Message-ID: | 200006141313.e5EDD9O14271@linda.lfix.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
>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(dot)Elphick(at)lfix(dot)co(dot)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 present your bodies a living sacrifice,
holy, acceptable unto God, which is your reasonable
service." Romans 12:1
From | Date | Subject | |
---|---|---|---|
Next Message | Murad Nayal | 2000-06-14 14:23:32 | info on unixODBC/Postgres driver port to IRIX 6.5.7 64bit |
Previous Message | Thomas Lockhart | 2000-06-14 12:56:54 | Re: Back online |
From | Date | Subject | |
---|---|---|---|
Next Message | David Reid | 2000-06-14 13:34:00 | BeOS and IPC - try 999 |
Previous Message | Bruce Momjian | 2000-06-14 04:52:38 | Re: Small patch for memory leak in src/backend/catalog/pg_proc.c |