From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <dhogaza(at)pacifier(dot)com>, <xun(at)cs(dot)ucsb(dot)edu>, <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | RE: [HACKERS] [hackers]development suggestion needed |
Date: | 2000-01-14 04:34:45 |
Message-ID: | 000401bf5e48$aecd2740$2801007e@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: owner-pgsql-hackers(at)postgreSQL(dot)org
> [mailto:owner-pgsql-hackers(at)postgreSQL(dot)org]On Behalf Of Tatsuo Ishii
>
>
> BTW, it would be nice to add a "table space" concept to the create
> table statement.
>
> -- reserve a table space named 'foo' which is physically located under
> -- /pg/myspace. Only PostgreSQL super user can execute this command
> -- to avoid security risks.
> create table space foo as '/pg/myspace';
>
> -- create table t1 under /pg/myspace
> create table t1 (i int) with table space 'foo';
> --
I agree with Tatsuo though I prefer
create table t1 (i int) tablespace foo;
.
Isn't it preferable to encapsulate the table location and storage type ?
At first,a tablespace would only correspond to a directory and it won't
be so difficult to implment. But we would gain a lot with the feature.
In the future,the tablespace may be changed to mean real(??)
tablespace.
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-01-14 04:41:05 | Re: Multiple Spindles ( Was: Re: [HACKERS] [hackers]development suggestion needed ) |
Previous Message | The Hermit Hacker | 2000-01-14 04:31:30 | Multiple Spindles ( Was: Re: [HACKERS] [hackers]development suggestion needed ) |