Re: BUG #15480: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range

From: Matthew Williams <mattyw(at)me(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pg(at)mattyw(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15480: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range
Date: 2018-11-01 14:39:18
Message-ID: 43D80FCA-97DB-4D96-8431-615856419BB6@me.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Apologies, I had an old safari tab open on the submission of the original bug (15471). It appears it's resubmitted the form.

Matt

> On 1 Nov 2018, at 10:26 pm, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> =?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
>> Below is an example .sql file that replicates the problem. Put simply, when
>> we array concat with enum_range in the result of a CASE statement the
>> concatenation takes the expression from the CASE statement, not the enum
>> range.
>
> Isn't this a duplicate of bug #15471 ?
>
> regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Gierth 2018-11-01 15:37:12 Re: BUG #15467: The database subdirectory "pg_tblspc/1932420460/PG_10_201707211/16400" is missing.
Previous Message Tom Lane 2018-11-01 14:26:54 Re: BUG #15480: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range