Re: BUG #19055: Server crash at ExecInterpExpr

Vik Fearing <vik@postgresfriends.org>

From: Vik Fearing <vik@postgresfriends.org>

To: dllggyx@outlook.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>

Date: 2025-09-17T17:57:14Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Calculate agglevelsup correctly when Aggref contains a CTE.
- e830896c16ee 17.7 landed
- b649ef2446a4 13.23 landed
- b0cc0a71e0a0 19 (unreleased) landed
- afd18f27615b 15.15 landed
- 7df74e635e65 16.11 landed
- 4eab456494e3 18.0 landed
- 31bf0963208f 14.20 landed

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