Re: BUG #19055: Server crash at ExecInterpExpr

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: dllggyx(at)outlook(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org>
Subject: Re: BUG #19055: Server crash at ExecInterpExpr
Date: 2025-09-17 17:57:14
Message-ID: 9221a173-b094-4063-8a02-0c8931d7b26c@postgresfriends.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


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(at)outlook(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-09-17 18:02:09 Re: BUG #19055: Server crash at ExecInterpExpr
Previous Message Masahiko Sawada 2025-09-17 16:00:36 Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary