From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18608: Assert in check_agglevels_and_constraints() fails on
 creating a rule with aggr(NEW) in subselect
In-reply-to: <18608-48de0717508ee429@postgresql.org>
References: <18608-48de0717508ee429@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 10 Sep 2024 18:00:01 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3543319.1725995180.1@sss.pgh.pa.us>
Date: Tue, 10 Sep 2024 15:06:20 -0400
Message-ID: <3543320.1725995180@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3543320.1725995180%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> [ NEW reference confuses check_agglevels_and_constraints ]

> triggers an assertion failure:
> TRAP: failed Assert("pstate->p_lateral_active"), File: "parse_agg.c", Line:
> 385, PID: 2785906

> Without asserts enabled, it fails with:
> ERROR:  aggregate functions are not allowed in FROM clause of their own
> query level

Interesting.  I'm inclined to just remove the Assert, since it's
evidently wrong and the ensuing error seems sufficiently on-point.

			regards, tom lane