|From:||Andres Freund <andres(at)anarazel(dot)de>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pg(at)mattyw(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org|
|Subject:||Re: BUG #15471: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2018-10-30 09:30:54 -0400, Tom Lane wrote:
> Good guess but I don't think that changed anything. It looks to me
> like the culprit is commit c12d570fa, so it's my bug not Andres' :-(.
> This is all some more fuel for the idea that we need a less messy
> substitute for CaseTestExpr. As it happens, I was just fooling with
> that yesterday, and hope to have something to post soon. But it'll
> be too invasive to back-patch. I'll try to fix this particular
> problem more locally.
Yea, I agree we need something better there. I happened to also play
around with that (more from the angle that we'd want similar
infrastructure for the SQL function inlining case we talked about) on
the long flights back from .eu yesterday, but didn't get that far. Will
wait till you have posted something.
|Next Message||PG Bug reporting form||2018-10-30 20:26:53||BUG #15472: Error creating postgis 2.5 extension in postgres 11|
|Previous Message||Andres Freund||2018-10-30 17:42:00||Re: BUG #15471: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range|