Re: Partitioning WIP patch

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Partitioning WIP patch
Date: 2015-02-25 20:15:43
Message-ID: 54EE2D6F.5000903@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-02-25 20:39:56 Re: CATUPDATE confusion?
Previous Message Tomas Vondra 2015-02-25 19:39:08 Re: Performance improvement for joins where outer side is unique