"cannot specify finite value after UNBOUNDED" ... uh, why?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: "cannot specify finite value after UNBOUNDED" ... uh, why?
Date: 2017-05-29 07:04:09
Message-ID: 28106.1496041449@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Would someone please defend the restrictions imposed by the
"seen_unbounded" checks in transformPartitionBound
(parse_utilcmd.c:3365..3396 in current HEAD)? They sure look to me like
nothing but sloppy thinking, and/or protection of downstream sloppy
thinking. Why should the boundedness of one partitioning column's
range matter to any other partitioning column's range?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2017-05-29 07:25:52 Macros bundling RELKIND_* conditions
Previous Message Beena Emerson 2017-05-29 06:55:15 Re: Adding support for Default partition in partitioning