From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Burd <greg(at)burd(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] bms_prev_member() can read beyond the end of the array of allocated words |
Date: | 2025-08-15 04:37:32 |
Message-ID: | CAApHDvorjk1ez2HPteCq=FRJEBR7RVogEHBO2OV9SAyO7DfHaw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 15 Aug 2025 at 15:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > I'm happy to push Greg's v5 patch if you have no counterarguments.
>
> In the end this isn't something I find worth arguing about. If
> you prefer v5, sure. I do suggest though that if we're installing
> Asserts at all, defending against prevbit < -1 is worth doing.
Agreed about defending against prevbit < -1. I added an Assert for
that. Technically, that Assert could be up above the if (a == NULL)
check, but I didn't think it mattered that much and opted to keep both
Asserts together. The difference being that bms_prev_member(NULL, -2)
will return -2 rather than Assert fail. I'm not too worried about
that, but if you feel strongly differently, I can adjust what I just
pushed.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Hayato Kuroda (Fujitsu) | 2025-08-15 04:46:17 | RE: Make pgoutput documentation easier to find |
Previous Message | Shinya Kato | 2025-08-15 04:19:02 | Re: Add mode column to pg_stat_progress_vacuum |