From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | cyg0810(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #17067: FailedAssertion at castNodeImpl |
Date: | 2021-06-21 11:13:43 |
Message-ID: | CAApHDvpbbF=KjstdD4Mq_XN2PS92PP3fAwFN+8ao8aF+dVvfsA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, 21 Jun 2021 at 22:10, Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> On Mon, Jun 21, 2021 at 5:48 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>> I'm quite surprised that we don't have a test that picks this up.
>
>
> A distinct group by clause would help to reveal this issue as:
>
> explain select * from t GROUP BY distinct a, rollup(b);
>
> Maybe we can add a test case to cover it.
Since beta2 deadline is looming, I pushed the simple fix for now. I'll
start a thread on hackers to ask the authors of the patch about
additional testing.
Yaoguang, the fix went in as of [1]. Thanks again for the report.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-06-21 13:33:29 | Re: BUG #17067: FailedAssertion at castNodeImpl |
Previous Message | Richard Guo | 2021-06-21 10:09:57 | Re: BUG #17067: FailedAssertion at castNodeImpl |