Re: A gap in preventing bogus parameterizations in a798660ebe3

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 18:07:22
Message-ID: 9709133f-9311-42a5-80f7-56741e0c850d@vondra.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/12/26 18:39, Tom Lane wrote:
> 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.
>

Thanks for reminding me, will fix.

--
Tomas Vondra

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Raja Sai pranav 2026-11-12 18:46:40 Re: Re: Assertion failure in WAL summarizer
Previous Message Bharath Rupireddy 2026-11-12 18:03:17 Re: pg_walinspect: fix LSN validation messages and empty range handling