From: | "Scott Marlowe" <smarlowe(at)qwest(dot)net> |
---|---|
To: | "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | swm(at)linuxworld(dot)com(dot)au, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] ALTER TABLE ... SET TABLESPACE |
Date: | 2004-06-21 00:35:15 |
Message-ID: | 1087778115.1187.3.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Sun, 2004-06-20 at 17:15, Tatsuo Ishii wrote:
> > > Also I think we need to enhance ALTER INDEX to assign new table spaces
> > > for indexes. Assigning different tables spaces for tables and indexes
> > > are essential to gain more I/O speed IMO.
> >
> > I thought about this. ALTER INDEX doesn't exist yet and I figured that,
> > unlike the case of tables, its easy to drop and recreate indexes in new
> > tablespaces.
>
> Oh you are right. I forgot about CREATE INDEX ... TABLESPACE.
>
> > I'm still stumped as to where I am corrupting memory with this patch
> > though. (There was another bug: I wasn't detecting the case where users
> > set tablespace to the tablespace that the table is already in).
On a related note, will there be a way to have implicit index creation
occur in a seperate table space automagically? I.e.
create table test (id int4 primary key, n1 int unique);
so that the indexes created in id and n1 here would have a different
default namespace than the table? Just wondering.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-21 00:49:22 | Re: nested xacts and phantom Xids |
Previous Message | Bruce Momjian | 2004-06-21 00:17:35 | Re: nested xacts and phantom Xids |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-21 00:49:22 | Re: nested xacts and phantom Xids |
Previous Message | Andrew Dunstan | 2004-06-21 00:21:17 | Re: Data directory with trailing [back]slash |