| From: | Michael Nolan <htfoot(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: problem/bug in drop tablespace? |
| Date: | 2012-05-08 14:09:41 |
| Message-ID: | CAOzAqu+tZTjORkGDZEUYpEVY0xf4TMBn2XBbv2=8fZ5Na-qEVg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The last portion of my original post got edited out by mistake.
The tests I ran were on version 9.1.3, running Fedora 14, kernel
2.6.35.14-106.fc14-i686.
It seems to me that DROP TABLESPACE should check to see if there are
references in the system catalog to the tablespace before dropping it, not
just that the tablespace itself is empty. That way it would have thrown an
error when I tried to drop the tablespace.
A somewhat separate issue is what to do when a tablespace is inaccessible,
such as due to a disk failure. The thread on -general that prompted my
tests was a relatively easy one to suggest how to repair, because the lost
tablespace only had indexes in it. But that's not exactly a -hackers
issue, more of a question of better backup protocols.
--
Mike Nolan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2012-05-08 17:59:32 | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |
| Previous Message | Etsuro Fujita | 2012-05-08 11:26:02 | WIP Patch: Selective binary conversion of CSV file foreign tables |