Re: BUG #18247: Integer overflow leads to negative width
RekGRpth <rekgrpth@gmail.com>
From: RekGRpth <rekgrpth@gmail.com>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org
Date: 2023-12-15T03:13:44Z
Lists: pgsql-bugs
How bad would it be if, after overflowing, the width value was within the allowed range? пт, 15 дек. 2023 г. в 07:28, Richard Guo <guofenglinux@gmail.com>: > > > On Thu, Dec 14, 2023 at 10:43 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> >> Richard Guo <guofenglinux@gmail.com> writes: >> > On Thu, Dec 14, 2023 at 5:29 PM PG Bug reporting form < >> > noreply@postgresql.org> wrote: >> >> EXPLAIN SELECT * FROM t; >> >> QUERY PLAN >> >> ------------------------------------------------------------ >> >> Seq Scan on t (cost=0.00..10.00 rows=1 width=-2113929008) >> >> (1 row) >> >> > Can we just error out when an overflow occurs? >> >> Probably better to clamp tuple width estimates to MaxAllocSize. >> Anything larger would not correspond to reality anyhow. > > > Fair point. How about the attached patch? > > Thanks > Richard
Commits
-
Prevent integer overflow when forming tuple width estimates.
- 7e1ce2b3de16 17.0 landed
-
compute_bitmap_pages' loop_count parameter should be double not int.
- 8b965c549dc8 17.0 landed