| From: | "Jim Buttafuoco" <jim(at)buttafuoco(dot)net> |
|---|---|
| To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>, "mlw" <markw(at)mohawksoft(dot)com>, <jim(at)buttafuoco(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Storage Location Patch Proposal for V7.3 |
| Date: | 2001-11-08 22:08:00 |
| Message-ID: | 200111082208.fA8M80C12797@dual.buttafuoco.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I am at home now, Tomorrow I will get the exact Oracle syntax and post
example commands for CREATE TABLESPACE, CREATE DATABASE, CREATE TABLE
and CREATE INDEX, CREATE USER.
Jim
>
> > Since "tablespace" is not part of the SQL standard, maybe it makes
> sense to
> > define a more specific syntax. The term "location" makes sense,
> because it is
> > not a tablespace as Oracle defines it.
>
> It *is* an "OS managed tablespace" in terms of IBM DB2.
> Methinks the term "TABLESPACE" is perfect for PostgreSQL.
> The fact whether it is a directory, a file or even a raw device
> depends on how you create the tablespace.
>
> The point is, that the syntax for "create table" and "create index"
> can be compatible in this case, imho without confusing many.
> Not the "create tablespace" syntax, but that is imho not an issue.
>
> Andreas
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-09 00:44:44 | Call for objections: revision of keyword classification |
| Previous Message | Evelio Martínez | 2001-11-08 19:52:45 | How to optimize a column type change??? |