On 2018/03/02 15:58, Andres Freund wrote: > On 2018-02-02 17:00:24 -0500, Tom Lane wrote: >> Peter Eisentraut <peter.eisentr...@2ndquadrant.com> writes: >>> There might be other options, but one way to solve this would be to >>> treat partition bounds as a general expression in the grammar and then >>> check in post-parse analysis that it's a constant. >> >> That's pretty much what I said upthread. What I basically don't like >> about the current setup is that it's assuming that the bound item is >> a bare literal. Even disregarding future-extension issues, that's bad >> because it can't result in an error message smarter than "syntax error" >> when someone tries the rather natural thing of writing a more complicated >> expression. > > Given the current state of this patch, with a number of senior > developers disagreeing with the design, and the last CF being in > progress, I think we should mark this as returned with feedback.
I see no problem with pursuing this in the next CF if the consensus is that we should fix how partition bounds are parsed, instead of adopting one of the patches to allow the Boolean literals to be accepted as partition bounds. For the latter, my patch [1] would do the job, although after posting that patch, the discussion turned into the one about the state of the current partition bound parsing code. I agree with most of the points raised and Horiguchi-san even came up with a not-so-invasive patch to do that, although, neither I, nor anyone else has been able to review or test it so far. I had written a patch like that one myself that I haven't shared on the list, but had seen some problems with it. I guess I should report those in reply to Horiguchi-san's post. That said, after seeing David Rowley's post earlier today [2], it seems that we may need to consider this issue a bug rather than a new feature. Thanks, Amit [1] https://www.postgresql.org/message-id/6844d7f9-8219-a9ff-88f9-82c05fc90d70%40lab.ntt.co.jp [2] https://www.postgresql.org/message-id/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com
