From: | Rick Gabriel <klaxian(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15208: COALESCE with CTE returns NULL |
Date: | 2018-05-25 17:48:45 |
Message-ID: | CACvJEPYimL3LdAgCXncyW2q3aEaPSo1RScGa12XrcpQs=30=aw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I'm very sorry to have bothered you. I thought this was a pg problem, but
it's not. It appears to be a bug in a GUI wrapper I'm using to issue the
queries. When using the psql client, everything works as expected. I will
file a separate bug report for the GUI. Please disregard this bug report.
On Fri, May 25, 2018 at 12:24 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:
> > When using COALESCE with an aggregate subquery to a CTE, NULL is returned
> > instead of the first non-null value in the argument list.
> Proof-of-concept
> > examples are below. I would expect COALESCE to return 0 in these cases.
> Am I
> > missing something? Thanks.
>
> Um ... I get zero from each of your test cases, in all PG versions back
> to 9.3.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2018-05-25 18:23:44 | BUG #15210: Internal Server Error When Attempting to Look at Trigger Functions |
Previous Message | PG Bug reporting form | 2018-05-25 16:57:41 | BUG #15209: Problem with string value in installer |