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

Re: Table Partitioning

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Table Partitioning
Date: 2011-06-23 14:18:15
Message-ID: BANLkTikYKeePVuw46oQz-tw0-BVBN3MvQg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Jun 21, 2011 at 1:52 PM, David Fetter <david(at)fetter(dot)org> wrote:
>> 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?

Yes, and I don't know, respectively.  There have been previous
discussions of this.  You might want to start by reading the
discussion around the previous patch.

https://commitfest.postgresql.org/action/patch_view?id=266

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Steve SingerDate: 2011-06-23 14:21:48
Subject: Re: Online base backup from the hot-standby
Previous:From: Robert HaasDate: 2011-06-23 14:12:49
Subject: Re: Hugetables question

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