Re: Multi column range partition table
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
From: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>, amul sul <sulamul@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-06-30T09:04:13Z
Lists: pgsql-hackers
On Fri, Jun 30, 2017 at 1:36 PM, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote: > > Alright, I spent some time implementing a patch to allow specifying > -infinity and +infinity in arbitrary ways. Of course, it prevents > nonsensical inputs with appropriate error messages. I don't think -infinity and +infinity are the right terms. For a string or character data type there is no -infinity and +infinity. Similarly for enums. We need to extend UNBOUNDED somehow to indicate the end of a given type in the given direction. I thought about UNBOUNDED LEFT/RIGHT but then whether LEFT indicates -ve side or +side would cause confusion. Also LEFT/RIGHT may work for a single dimensional datatype but not for multi-dimensional spaces. How about MINIMUM/MAXIMUM or UNBOUNDED MIN/MAX to indicate the extremities. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
Commits
-
Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition bounds.
- d363d42bb9a4 10.0 landed
-
Clarify the contract of partition_rbound_cmp().
- f1dae097f294 10.0 landed
-
Simplify the logic checking new range partition bounds.
- c03911d9454a 10.0 landed