Fabien COELHO <fabien(dot)coelho(at)ensmp(dot)fr> writes:
>> The sequences are in the same tablespace as the system catalogs of the
>> database they are in, so this objection is moot.
> three (unusual?) commands to reach the "moot" state:
> psql> CREATE TABLESPACE foo LOCATION '/tmp/postgres';
> psql> CREATE SCHEMA bla TABLESPACE foo;
> 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. The intention was that sequences would always be
in the database default tablespace. I'm not sure why this case is
overriding that ... but we can fix it.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Fabien COELHO||Date: 2004-08-31 15:01:19|
|Subject: Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
|Previous:||From: Bruce Momjian||Date: 2004-08-31 11:44:17|
|Subject: Win32 compile and beta2|
pgsql-patches by date
|Next:||From: Ed L.||Date: 2004-08-31 14:45:18|
|Subject: Re: log_filename_prefix --> log_filename + strftime()|
|Previous:||From: Shinji Teragaito||Date: 2004-08-31 11:00:14|
|Subject: Re: [PATCHES] HP-UX PA-RISC/Itanium 64-bit Patch and HP-UX 11.23 Patch |