Re: bug in DROP TABLESPACE - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: bug in DROP TABLESPACE
Date
Msg-id 40EB5FDF.8060903@familyhealth.com.au
Whole thread Raw
In response to Re: bug in DROP TABLESPACE  (Gavin Sherry <swm@linuxworld.com.au>)
Responses ALTER xxx SET TABLESPACE (was bug in DROP TABLESPACE)  (Andreas Pflug <pgadmin@pse-consulting.de>)
Re: bug in DROP TABLESPACE  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: bug in DROP TABLESPACE  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> Tom already mentioned this just after committing tablespaces: 'Minor DROP
> TABLESPACE issue'
> 
> http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg46540.html
> 
> In fact, I see that you contributed to the thread :-).
> 
> I think the result of the thread was to make the error message a little
> more helpful and that adding empty files to represent schemas would be a
> pain (think WAL and name collision).

Ah, I must have been in a dream state.

The other thing we need are these two commands:

ALTER DATABASE foo SET TABLESPACE spc;
ALTER SCHEMA foo SET TABLESPACE spc;

I think these should not be considered new features but essential 
functionality left out of the original patch.

Chris



pgsql-hackers by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Re: [Re] Re: PREPARE and transactions
Next
From: "Scott Marlowe"
Date:
Subject: Re: Nested Transactions, Abort All