Postgres Pro
Downloads
Home   >   mailing lists

[HACKERS] "cannot specify finite value after UNBOUNDED" ... uh, why? - Mailing list pgsql-hackers

From Tom Lane
Subject [HACKERS] "cannot specify finite value after UNBOUNDED" ... uh, why?
Date
Msg-id 28106.1496041449@sss.pgh.pa.us
Whole thread Raw
Responses Re: [HACKERS] "cannot specify finite value after UNBOUNDED" ... uh,why?  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Re: [HACKERS] "cannot specify finite value after UNBOUNDED" ... uh, why?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Beena Emerson
Date:
Subject: Re: [HACKERS] Adding support for Default partition in partitioning
Next
From: Ashutosh Bapat
Date:
Subject: [HACKERS] Macros bundling RELKIND_* conditions