Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
Ashutosh Sharma <ashu.coek88@gmail.com>
From: Ashutosh Sharma <ashu.coek88@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: surya poondla <suryapoondla4@gmail.com>, "violin0613@tju.edu.cn" <violin0613@tju.edu.cn>, pgsql-bugs@postgresql.org
Date: 2026-06-05T08:00:42Z
Lists: pgsql-bugs
Hi Michael, Thanks for the patch. On Fri, Jun 5, 2026 at 12:27 PM Michael Paquier <michael@paquier.xyz> wrote: > > On Fri, Jun 05, 2026 at 08:17:15AM +0900, Michael Paquier wrote: > > At the end, the first pattern is an outlier, we don't need to worry > > about performance in pg_surgery, and we're talking about three lines > > of code in pg_surgery to change (two for include_this_tid, one for the > > assertion). With all that in mind, I'd just do a -1 conversion and > > call it a day. :) > > Which implies something like the simpler patch attached. I have one small comment: "+ Assert((offno - 1) < MaxHeapTuplesPerPage);" I think this can be simplified to: Assert(offno <= MaxHeapTuplesPerPage); Since "offno" is already 1-based, there doesn't seem to be a need to subtract 1 from it and adjust the comparison accordingly. -- With Regards, Ashutosh Sharma.
Commits
-
pg_surgery: Fix off-by-one bug with heap offset
- 1eda3eb0753a 14 (unreleased) landed
- 51f63ba2bf7f 15 (unreleased) landed
- daf8bc7d41ac 16 (unreleased) landed
- 0bcf19c9e8fc 17 (unreleased) landed
- 2b09f8a9110a 18 (unreleased) landed
- 193a4ded9474 19 (unreleased) landed