| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | rekgrpth(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18247: Integer overflow leads to negative width |
| Date: | 2023-12-14 14:43:45 |
| Message-ID: | 2781181.1702565025@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> On Thu, Dec 14, 2023 at 5:29 PM PG Bug reporting form <
> noreply(at)postgresql(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-12-14 14:50:01 | Re: BUG #18245: pg_restore accepts same output file name as input file name |
| Previous Message | Tom Lane | 2023-12-14 14:40:48 | Re: BUG #18248: Expression is always zero |