From: | Shane Ambler <pgsql(at)Sheeky(dot)Biz> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Luke Lonergan <llonergan(at)greenplum(dot)com>, Zeugswetter Andreas ADI SD <ZeugswetterA(at)spardat(dot)at>, NikhilS <nikkhils(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Auto creation of Partitions |
Date: | 2007-03-08 20:10:29 |
Message-ID: | 45F06DB5.1010207@Sheeky.Biz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> Note to Nikhil: Make sure the new syntax doesn't prevent partitions from
> being placed upon multiple tablespaces in some manner, at CREATE TABLE
> time.
What if the syntax was something like -
CREATE TABLE tabname (
...
...
) PARTITION BY
HASH(expr)
| RANGE(expr)
| LIST(expr)
[PARTITIONS num_partitions] /* will apply to HASH only for now*/
[PARTITION partition_name CHECK(...) [USING TABLESPACE tblspcname],
PARTITION partition_name CHECK(...) [USING TABLESPACE tblspcname]
...
];
And (if we use the ALTER TABLE to add partitions)
ALTER TABLE tabname
ADD PARTITION partition_name CHECK(...)
[USING TABLESPACE tblspcname];
Of course ALTER TABLE childtable SET TABLESPACE tblspcname; should not
cause any probs.
--
Shane Ambler
pgSQL(at)Sheeky(dot)Biz
Get Sheeky @ http://Sheeky.Biz
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Bird | 2007-03-08 20:11:43 | Re: who gets paid for this |
Previous Message | Christian Bird | 2007-03-08 20:10:22 | who gets paid for this |
From | Date | Subject | |
---|---|---|---|
Next Message | Shane Ambler | 2007-03-08 22:01:10 | Re: Auto creation of Partitions |
Previous Message | Doug Knight | 2007-03-08 19:33:46 | Re: [PATCHES] pg_standby |