Re: Pg18 Recursive Crash - Mailing list pgsql-hackers

From David Rowley
Subject Re: Pg18 Recursive Crash
Date
Msg-id CAApHDvoAVy4v8Mm7nPi-qCBp+9b_9OhdT93A8NJ2gnc_zbq5AA@mail.gmail.com
Whole thread Raw
In response to Re: Pg18 Recursive Crash  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On Tue, 17 Dec 2024 at 07:10, Nathan Bossart <nathandbossart@gmail.com> wrote:
> On Mon, Dec 16, 2024 at 09:50:39AM -0800, Paul Ramsey wrote:
> > CREATE TABLE foo (id integer, x integer, y integer);
> > INSERT INTO foo VALUES (1, 0, 1);
> > INSERT INTO foo VALUES (2, 1, 2);
> > INSERT INTO foo VALUES (3, 2, 3);
> >
> > WITH RECURSIVE path (id, x, y) AS (
> >     SELECT id, x, y FROM foo WHERE id = 1
> >     UNION
> >     SELECT foo.id, foo.x, foo.y
> >     FROM path, foo
> >     WHERE path.y = foo.x
> > )
> > SELECT 'crash', id, x, y FROM path;
>
> git-bisect is pointing me to https://postgr.es/c/0f57382.  Here is the
> trace I'm seeing:

Thanks for the report and bisection. Looking now.

David



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Improving default column names/aliases of subscript text expressions
Next
From: Joe Conway
Date:
Subject: Re: Add CASEFOLD() function.