On Mon, Mar 25, 2024 at 8:02 AM Masahiko Sawada <sawada.m...@gmail.com> wrote: > > On Mon, Mar 25, 2024 at 1:53 AM Tom Lane <t...@sss.pgh.pa.us> wrote: > > > > I'm not sure why it took a couple weeks for Coverity to notice > > ee1b30f12, but it saw it today, and it's not happy: > > Hmm, I've also done Coverity Scan in development but I wasn't able to > see this one for some reason...
Hmm, before 30e144287 this code only ran in a test module, is it possible Coverity would not find it there?
