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.
