Re: BUG #18924: The "ERROR: integer out of range" should be more detailed - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #18924: The "ERROR: integer out of range" should be more detailed
Date
Msg-id CAKFQuwa96gN7P4Exi_iNVJv=CwWdVZ9ZRU=sn084GRyy-Bm=Hw@mail.gmail.com
Whole thread Raw
In response to BUG #18924: The "ERROR: integer out of range" should be more detailed  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Monday, May 12, 2025, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      18924
Logged by:          Adrien Ducos
Email address:      sysgeo@gmail.com
PostgreSQL version: 17.4
Operating system:   aarch64-unknown-linux-gnu (AWS RDS)
Description:       

--ERROR: integer out of range
The problem here is not that the integer is out of range (5 billion is out
of range for the integer type). The problem is that the error message does
not tell me where the error is in the query.


This is a known limitation that is looking for someone(s) to volunteer to do some hard design and development work to overcome.

Some existing thoughts on the topic can be found by searching these mailing lists.

David J.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always
Next
From: Tom Lane
Date:
Subject: Re: BUG #18923: pg_dump 18beta1 fails to process complex table names