Re: Partitioning WIP patch - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Partitioning WIP patch
Date
Msg-id 54EE2D6F.5000903@agliodbs.com
Whole thread Raw
In response to Partitioning WIP patch (was: Partitioning: issues/ideas)  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: Partitioning WIP patch  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On 02/24/2015 12:13 AM, Amit Langote wrote:
> Here is an experimental patch that attempts to implement this.

This looks awesome.  I would love to have it for 9.5, but I guess the
patch isn't nearly baked enough for that?

> It implements the following syntax:
> 
> * Syntax for defining partition key:
> CREATE TABLE table_name(columns)PARTITION BY {RANGE|LIST} ON (key_spec);
> 
> where key_spec consists of partition key column names and optional
> operator class per column. Currently, there are restrictions on the
> key_spec such as allowing only column names (not arbitrary expressions
> of them), only one column for list strategy, etc.

What's the obstacle to supporting expressions and/or IMMUTABLE
functions?  I think it's fine to add this feature without them
initially, I'm just asking about the roadmap for eventually supporting
expressions in the key spec.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Performance improvement for joins where outer side is unique
Next
From: Stephen Frost
Date:
Subject: Re: CATUPDATE confusion?