Christopher Kings-Lynne wrote:
> >>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...
This is going to have to wait for 8.1. If it was so important, someone
would have asked for it long before we went beta. It is now on the TODO
list.
Also, I question the value of being able to change the default but not
being able to move the schema contents. In fact, I can't think of any
other case where we change the default for new objects but leave the old
objects with their original settings. This all needs discussion for
8.1.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073