Re: Possible integer overflow in bringetbitmap()
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: James Hunter <james.hunter.pg@gmail.com>
Cc: Evgeniy Gorbanyov <gorbanyoves@basealt.ru>, pgsql-hackers@lists.postgresql.org
Date: 2024-12-20T23:22:22Z
Lists: pgsql-hackers
On Tue, Dec 10, 2024 at 12:33:08PM +0900, Michael Paquier wrote: > Sure, you could do (a) and (b) together. It also seems to me that it > is just simpler to make totalpages a int64 to map automatically with > the result expected by the caller of bringetbitmap(), and we know that > based on MaxBlockNumber we'll never run out of bits. That should be simple enough. Are you planning to send a proposal of patch? -- Michael
Commits
-
Fix potential integer overflow in bringetbitmap()
- 332023e2d032 13.19 landed
- e35ff6520569 14.16 landed
- 9e9f30139eb8 15.11 landed
- bfda7d8dd6b3 16.7 landed
- e027ee9902fa 17.3 landed
- 720e529840d5 18.0 landed