Re: Declarative partitioning grammar

From: Gavin Sherry <swm(at)alcove(dot)com(dot)au>
To: NikhilS <nikkhils(at)gmail(dot)com>
Cc: Jeff Cohen <jcohen(at)greenplum(dot)com>, Warren Turkal <turkal(at)google(dot)com>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Declarative partitioning grammar
Date: 2008-01-14 23:41:30
Message-ID: 20080114234130.GJ7216@europa.idg.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 12, 2008 at 04:01:19PM +0530, NikhilS wrote:
> 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.

In some prototyping code it didn't seem too difficult but if we've made
a mistake we might have to look at the CE code.

Thanks,

Gavin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-01-14 23:48:19 Re: Bug: Unreferenced temp tables disables vacuum to update xid
Previous Message Alvaro Herrera 2008-01-14 23:38:02 Re: Bug: Unreferenced temp tables disables vacuum to update xid