Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Vik Fearing <vik(at)postgresfriends(dot)org>, Kamil Monicz <kamil(at)monicz(dot)dev>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
Date: 2025-11-18 17:59:34
Message-ID: 1302816.1763488774@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> The more I think about this, the more I like the other idea of just
> throwing an error rather than trying to fix up cases like bug #19055.
> I don't think we have much evidence that anyone is trying to do that
> in the real world (otherwise reports would have surfaced years ago).
> And this discussion is making it clear that fixing it up is harder
> than it sounds.

Hearing no further comments, I've pushed the v2 patch that does it
that way, restoring the previous behavior in cases that would not
have failed before #19055.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Devrim Gündüz 2025-11-18 21:02:20 Re: BUG #19113: Missing updated libpq5 rpm in repo pgdg-common after minor release to 18.1
Previous Message Devrim Gündüz 2025-11-18 16:56:43 Re: BUG #19117: postgresql15-contrib-15.15 for RHEL 9 has conflicting OpenSSL dependencies (3.0.0 and 3.4.0)