Re: Multi column range partition table
Dean Rasheed <dean.a.rasheed@gmail.com>
From: Dean Rasheed <dean.a.rasheed@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>,
amul sul <sulamul@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-07-06T20:24:07Z
Lists: pgsql-hackers
On 6 July 2017 at 21:04, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Dean Rasheed <dean.a.rasheed@gmail.com> writes: >> However, this is also an incompatible syntax change, and any attempt >> to support both the old and new syntaxes is likely to be messy, so we >> really need to get consensus on whether this is the right thing to do, >> and whether it *can* be done now for PG10. > > FWIW, I'd much rather see us get it right the first time than release > PG10 with a syntax that we'll regret later. I do not think that beta2, > or even beta3, is too late for such a change. > > I'm not taking a position on whether this proposal is actually better > than what we have. But if there's a consensus that it is, we should > go ahead and do it, not worry that it's too late. > OK, thanks. That's good to know. Regards, Dean
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