Re: BUG #16978: Nested CTEs give ERROR in v13

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: tharakan(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16978: Nested CTEs give ERROR in v13
Date: 2021-04-23 14:56:03
Message-ID: 20210423145603.GC7629@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Apr 23, 2021 at 10:08:06AM -0400, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > This narrowed down SQL (from what SQLSmith generated) seems to error out
> > only with N levels of CTE nesting - no tables / views / 1-row output.
> > The SQL works fine with v12.4 but raises an ERROR in v13 which seems like a
> > regression. Is this owing a recent change in v13 - that could affect this?
>
> FWIW, I don't see any error from this, either in HEAD or the
> back branches.
>
> $ cat recursive.sql
> WITH RECURSIVE w6(c6) AS
> (WITH w6(c6) AS
> (WITH w8(c8) AS
> (WITH w9(c9) AS
> (WITH w10(c10) AS
> (WITH w11(c11) AS
> (WITH w_err(c12) AS
> (SELECT 1)
> SELECT * FROM w_err)
> SELECT * FROM w11)
> SELECT * FROM w10)
> SELECT * FROM w9)
> SELECT * FROM w8)
> SELECT * FROM w6)
> SELECT * FROM w6;
> $ psql -f recursive.sql
> c6
> ----
> 1
> (1 row)

Uh, I don't see the failure in 13 head or master, but I do see it from a
13.2 tree checkout. I will try to find the post-13.2 commit cause.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry Dolgov 2021-04-23 15:15:05 Re: XX000: unknown type of jsonb container.
Previous Message Tom Lane 2021-04-23 14:11:20 Re: BUG #16979: WITH RECURSIVE SQL crashes v13.x