Skip site navigation (1) Skip section navigation (2)

Re: Declarative partitioning grammar

From: NikhilS <nikkhils(at)gmail(dot)com>
To: "Jeff Cohen" <jcohen(at)greenplum(dot)com>
Cc: "Warren Turkal" <turkal(at)google(dot)com>, "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>, "Gavin Sherry" <swm(at)alcove(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Declarative partitioning grammar
Date: 2008-01-12 10:31:19
Message-ID: d3c4af540801120231u6eed4a5v365288ea6991cd31@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi,

> We did look at allowing general functions for partitioning and this
> was one concern.  The other is that we want to enforce that a row
> only gets inserted into a single partition, so we wanted a
> declarative syntax where it was relatively easy to check that range
> and list specifications don't overlap.
>

Detection of mutually exclusive ranges might not turn out to be so easy
afterall. I think there is some code in the constraint_exclusion area which
might help out in this.

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

In response to

Responses

pgsql-hackers by date

Next:From: NikhilSDate: 2008-01-12 10:40:46
Subject: Re: Declarative partitioning grammar
Previous:From: NikhilSDate: 2008-01-12 10:24:25
Subject: Re: Declarative partitioning grammar

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group