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

From Bruce Momjian
Subject Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE
Date
Msg-id 200408202007.i7KK7X518285@candle.pha.pa.us
Whole thread Raw
In response to Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE  (Philip Warner <pjw@rhyme.com.au>)
Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
Marc G. Fournier wrote:
> On Fri, 20 Aug 2004, Bruce Momjian wrote:
> 
> > Would people like this applied to 8.0?  It addresses another of the
> > tablespace deficiency.
> 
> 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.

Added to TODO:

>       o Allow databases and schemas to be moved to different tablespaces
>
>       One complexity is whether moving a schema should move all existing
>       schema objects or just define the location for future object creation.

--  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
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: pg_dump print error location
Next
From: Tom Lane
Date:
Subject: Re: pg_subtrans and WAL