Horton

Re: On partitioning

Jim Nasby <jim.nasby@bluetreble.com>

View thread View on postgr.es
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Robert Haas <robertmhaas@gmail.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Andres Freund <andres@2ndquadrant.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2014-12-12T21:28:33Z
Lists: pgsql-hackers 
On 12/12/14, 8:03 AM, Robert Haas wrote:
> On Thu, Dec 11, 2014 at 11:43 PM, Amit Langote
> <Langote_Amit_f8@lab.ntt.co.jp>  wrote:
>> >In case of what we would have called a 'LIST' partition, this could look like
>> >
>> >... FOR VALUES (val1, val2, val3, ...)
>> >
>> >Assuming we only support partition key to contain only one column in such a case.
>> >
>> >In case of what we would have called a 'RANGE' partition, this could look like
>> >
>> >... FOR VALUES (val1min, val2min, ...) TO (val1max, val2max, ...)
>> >
>> >How about BETWEEN ... AND ... ?
> Sure.  Mind you, I'm not proposing that the syntax I just mooted is
> actually for the best.  What I'm saying is that we need to talk about
> it.

Frankly, if we're going to require users to explicitly define each partition then I think the most appropriate API would be a function. Users will be writing code to create new partitions as needed, and it's generally easier to write code that calls a function as opposed to glomming a text string together and passing that to EXECUTE.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com