Re: Pg18 Recursive Crash

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Paul Ramsey <pramsey@cleverelephant.ca>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-12-16T21:20:46Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Optimize grouping equality checks with virtual slots

  2. Fix Assert failure in WITH RECURSIVE UNION queries

  3. Fix incorrect slot type in BuildTupleHashTableExt

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