| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Allow DROP TABLESPACE to succeed (with a warning) if the |
| Date: | 2007-03-22 19:51:44 |
| Message-ID: | 20070322195144.BB1969FB9B4@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Allow DROP TABLESPACE to succeed (with a warning) if the pg_tblspc symlink
doesn't exist. This allows DROP to be used to clean out the pg_tablespace
catalog entry in a situation where a previous DROP attempt failed before
committing but after having removed the directories and symlink.
Per report from William Garrison. Even though his test case depends on an
unrelated bug in PreventTransactionChain, it's certainly possible for this
situation to arise due to other problems, eg a system crash at just the
right time.
Modified Files:
--------------
pgsql/src/backend/commands:
tablespace.c (r1.44 -> r1.45)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablespace.c.diff?r1=1.44&r2=1.45)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-03-22 19:53:31 | pgsql: Allow the pgstat process to restart immediately after a receiving |
| Previous Message | Bruce Momjian | 2007-03-22 19:42:03 | pgsql: Properly enforce pg_dump -F formation options; only single letter |