| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru> |
| Subject: | Re: [PoC] Improve dead tuple storage for lazy vacuum |
| Date: | 2024-03-25 01:14:06 |
| Message-ID: | CANWCAZZ5Jrbi3R6+9JaN0G8Rwww+oGEV_UDsPxA__xEVs7rwdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 25, 2024 at 8:02 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> On Mon, Mar 25, 2024 at 1:53 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Japin Li | 2024-03-25 01:24:58 | Re: Cannot find a working 64-bit integer type on Illumos |
| Previous Message | Tom Lane | 2024-03-25 01:13:24 | Re: [PoC] Improve dead tuple storage for lazy vacuum |