Re: BUG #17067: FailedAssertion at castNodeImpl

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <dgrowleyml(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 13:33:29
Message-ID: 1641484.1624282409@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> On Mon, 21 Jun 2021 at 20:15, PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
>> run the following sql command through client and the PostgreSQL database
>> process will crash:

> Thanks for the report. It looks like a thinko in 1d581ce71. Code
> was added there which insists the initial list element is a List, but
> it's an IntList. I think the code should just use linitial instead of
> linitial_node.

Hmm, if it's an int-list then the subsequent dup-elimination loop is
also wrong, and for that matter I don't think the preceding lines
would have worked.

> I'm quite surprised that we don't have a test that picks this up.

The code coverage report shows that we *do* have tests that run
through this code, so the existing typing is okay in the test cases
we have. I'm guessing the real problem is that something upstream is
generating the wrong type of list in this example.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2021-06-21 14:18:33 Re: BUG #17067: FailedAssertion at castNodeImpl
Previous Message David Rowley 2021-06-21 11:13:43 Re: BUG #17067: FailedAssertion at castNodeImpl