PG Bug reporting form <noreply@postgresql.org> writes:
> After upgrading to Postgres 18 I've come across an error I wasn't getting
> beforehand. Here's a minimal way to reproduce the issue, that used to work
> well in Postgres 12 and 17 at least.
Thank you for this well-crafted bug report! Bisecting shows that
it broke at
f5050f795aea67dfc40bbc429c8934e9439e22e7 is the first bad commit
commit f5050f795aea67dfc40bbc429c8934e9439e22e7 (HEAD)
Author: Richard Guo <rguo@postgresql.org>
Date: Tue Sep 10 12:36:48 2024 +0900
Mark expressions nullable by grouping sets
I have not dug any deeper than that.
regards, tom lane