Re: A gap in preventing bogus parameterizations in a798660ebe3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Richard Guo <guofenglinux(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Tender Wang <tndrwang(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A gap in preventing bogus parameterizations in a798660ebe3
Date: 2026-11-12 17:39:42
Message-ID: 46500.1794505182@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tomas(at)vondra(dot)me> writes:
> Pushed, after rewording the commit message a little bit to make it clear
> we were not rejecting the paths, but a final plan would not have used
> them because of the bogus parameterization.

The buildfarm is pointing out that this change requires updating
.abi-compliance-history in the back branches.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-11-12 17:57:58 Re: [PATCH] Report malformed integer aggregate states as array errors
Previous Message Strydom, Matthys 2026-11-12 17:17:00 Re: [PATCH] Report malformed integer aggregate states as array errors