Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE - Mailing list pgsql-hackers

From Robert Treat
Subject Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE
Date
Msg-id 200408222316.59137.xzilla@users.sourceforge.net
Whole thread Raw
In response to Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
On Sunday 22 August 2004 21:34, Marc G. Fournier wrote:
> On Mon, 23 Aug 2004, 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...
>
> If they just created the schema, then a dump/reload would fix it ...
>

A dump/reload can fix a lot of problems... of course the people who are most 
likely to use tablespaces are probably the same people most likely to not be 
able to do a dump/reload just after doing the dump/reload they had to do to 
upgrade to 8.0.  Hopefully they'll have more forsight than we did...

-- 
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE
Next
From: "Marc G. Fournier"
Date:
Subject: Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE