From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
Date: | 2004-08-31 15:01:19 |
Message-ID: | Pine.LNX.4.58.0408311650050.28337@sablons.cri.ensmp.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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...
> but we can fix it.
Good.
--
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr
From | Date | Subject | |
---|---|---|---|
Next Message | Katsaros Kwn/nos | 2004-08-31 17:17:59 | Storing a query plan... |
Previous Message | Tom Lane | 2004-08-31 14:31:03 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-31 18:57:28 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
Previous Message | Ed L. | 2004-08-31 14:48:36 | Re: log_filename_prefix --> log_filename + strftime() |