Re: BUG #19492: intarray: fix variable stats leak in _int_matchsel

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: zengman <zengman(at)halodbtech(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19492: intarray: fix variable stats leak in _int_matchsel
Date: 2026-05-25 22:17:25
Message-ID: 210876.1779747445@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"=?gb18030?B?emVuZ21hbg==?=" <zengman(at)halodbtech(dot)com> writes:
> Patch attached. Also added a test case that exercises this code path
> by creating a text operator with _int_matchsel as the restriction
> estimator.

Good catch, pushed. I didn't bother with the test case though ---
none of the other early exits in that function have test cases,
and I don't see why this one is any more fragile than the others.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Matheus Alcantara 2026-05-25 22:26:17 Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
Previous Message Tom Lane 2026-05-25 21:23:27 Re: BUG #19486: Regression in SQL-language functions using XML values and IS DOCUMENT