Re: Table Partitioning

From: David Fetter <david(at)fetter(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Table Partitioning
Date: 2011-06-21 17:52:38
Message-ID: 20110621175238.GA7879@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 21, 2011 at 01:07:17PM -0400, Robert Haas wrote:
> On Mon, Jun 20, 2011 at 5:42 PM, David Fetter <david(at)fetter(dot)org> wrote:
> > I noticed that we have some nice new speed optimizations (more
> > properly, de-pessimizations) for partitioned tables in 9.1.
>
> /me sticks tongue out at dfetter.
>
> > Anybody care to look over the table partitioning stuff on the wiki and
> > check it for relevance?
> >
> > http://wiki.postgresql.org/wiki/Table_partitioning
>
> Itagaki Takahiro had a patch for this about a year ago, but I wasn't
> happy with the system catalog representation he chose and I think
> there were some other issues as well.

In particular, I'm noticing things labeled 8.4 and 9.0 as future.

> Still, I think a pretty clear
> way forward here is to try to figure out a way to add some explicit
> syntax for range partitions, so that you can say...
>
> foo_a is for all rows where foo starts with 'a'
> foo_b is for all rows where foo starts with 'b'
> ...
> foo_xyz is for all rows where foo starts with 'xyz'
>
> If we have that data represented explicitly in the system catalog,
> then we can look at doing built-in INSERT-routing and UPDATE-handling.
> For an added bonus, it's a more natural syntax.

Does someone else have such a syntax? Does The Standardâ„¢ have
anything to say?

Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-06-21 18:24:31 Re: ALTER TABLE lock strength reduction patch is unsafe
Previous Message Alvaro Herrera 2011-06-21 17:13:08 Re: ALTER TABLE lock strength reduction patch is unsafe