Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Rahul <rahul(at)rhyadav(dot)dev>, Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>, Samuel Olaoye <dapsalmy(at)gmail(dot)com>, Pgsql Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
Date: 2026-10-31 04:49:22
Message-ID: CAGRkXqSBor-XPjAO-_=oUkm56STpQCRc3toLJiKqW-xYMOwZXg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Richard,

v3 looks right to me. Each reference gets its own flag, so the
rescan order does not matter.

I did some experiment on your patch and also tested JIT on it, everything
looks good

Thanks,
Shihao

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Michael Paquier 2026-10-31 00:28:34 Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)