This is an extension of tablespaces, and is not required to fix a bug ... therefore, it is a feature, and not eligible for inclusion at this point in the development cycle ...
I am inclined to agree. ALTER INDEX is an operation that will happen quite often, but I don't think ALTER SCHEMA will be as frequent, and the given solution doesn't address the two needs of moving the entire schema or just future object creation.
No, it implements something that is currently impossible without editing the system catalogs - clearly an oversight! Especially if we add a disk-based change to it to avoid those drop tablespace errors.
It will be 5 minutes before someone who has created a schema in 8.0 and then will want to make it have a different default - there's no way they can do it...
Chris
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
