Re: BUG #18247: Integer overflow leads to negative width
От | RekGRpth |
---|---|
Тема | Re: BUG #18247: Integer overflow leads to negative width |
Дата | |
Msg-id | CAPgh2mKOawDQbmrtxXv_rOCSNAo4ByorMDGHdvy=Gs7ub734tw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18247: Integer overflow leads to negative width (Richard Guo <guofenglinux@gmail.com>) |
Ответы |
Re: BUG #18247: Integer overflow leads to negative width
|
Список | 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
В списке pgsql-bugs по дате отправления: