Message-ID: <9221a173-b094-4063-8a02-0c8931d7b26c@postgresfriends.org>
Date: Wed, 17 Sep 2025 19:57:14 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: BUG #19055: Server crash at ExecInterpExpr
To: dllggyx@outlook.com, pgsql-bugs@lists.postgresql.org,
 PG Bug reporting form <noreply@postgresql.org>
References: <19055-6970cfa8556a394d@postgresql.org>
Content-Language: en-US
From: Vik Fearing <vik@postgresfriends.org>
In-Reply-To: <19055-6970cfa8556a394d@postgresql.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/9221a173-b094-4063-8a02-0c8931d7b26c%40postgresfriends.org>
Precedence: bulk


On 17/09/2025 16:34, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference:      19055
> Logged by:          BugForge
> Email address:      dllggyx@outlook.com
> PostgreSQL version: 17.6
> Operating system:   Ubuntu 20.04 x86-64, docker image postgres:17.6
> Description:
>
> PoC:
> SELECT FROM ( SELECT generate_series ( 1 , '31' ) x ) GROUP BY ( x ) WINDOW
> w AS ( ORDER BY ( WITH x AS ( WITH x AS ( SELECT sum ( x ) ) SELECT DISTINCT
> * FROM x ) ( SELECT ( count ( ( SELECT x FROM x ) ) ) ) ) )


This query seems to crash the server at least back to 16.  The only 
simplification of it that I could manage was to replace generate_series 
with SELECT 1.  I could also replace all of the x's with different names 
without effect.

-- 

Vik Fearing