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

From Bruce Momjian
Subject Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE
Date
Msg-id 200408311857.i7VIvSS14429@candle.pha.pa.us
Whole thread Raw
In response to Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Fabien COELHO wrote:
> 
> Dear Tom,
> 
> > >     psql> CREATE TABLE bla.boo(id SERIAL PRIMARY KEY);
> >
> > > Now you have schema bla, table bla.boo, index bla.boo_pkey and sequence
> > > bla.boo_id_seq all in tablespace foo.
> >
> > Hmm, that's a bug.
> 
> If you consider that a bug, then you can also add: "CREATE SEQUENCE bla.sg;"
> 
> > The intention was that sequences would always be in the database default
> > tablespace.  I'm not sure why this case is overriding that ...
> 
> It does what the doc says about schema tablespaces:
> 
>   "The name of the tablespace that is to be the default tablespace for
>   all new objects created in the schema. If not supplied, the schema will
>   inherit the default tablespace of the database."
> 
> and that looks sound enough to me...

Good point.  If we put sequences in the database default location it
would be inconsistent with other object location, but this does bring up
the problem of being unable to move sequences to get rid of a
tablespace.

--  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: "Joshua D. Drake"
Date:
Subject: Re: Storing a query plan...
Next
From: Tom Lane
Date:
Subject: Still a loose end in GUC USERLIMIT stuff