Re: Auto creation of Partitions

From: NikhilS <nikkhils(at)gmail(dot)com>
To: "Shane Ambler" <pgsql(at)sheeky(dot)biz>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Luke Lonergan" <llonergan(at)greenplum(dot)com>, "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Auto creation of Partitions
Date: 2007-03-09 06:18:34
Message-ID: d3c4af540703082218k1bf6a0ecw784bfb023eaab8b5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Hi,

On 3/9/07, Shane Ambler <pgsql(at)sheeky(dot)biz> wrote:
>
>
> > 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];
>
>
We could as well drop the USING part.

Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message NikhilS 2007-03-09 06:23:04 Re: Auto creation of Partitions
Previous Message Josh Berkus 2007-03-09 05:51:41 Re: who gets paid for this

Browse pgsql-patches by date

  From Date Subject
Next Message NikhilS 2007-03-09 06:23:04 Re: Auto creation of Partitions
Previous Message Tatsuhito Kasahara 2007-03-09 04:14:51 Re: Patch for pgstatindex to fix a bug reporting a value of strange leaf_fragmentation