| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "sysgeo(at)gmail(dot)com" <sysgeo(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18924: The "ERROR: integer out of range" should be more detailed |
| Date: | 2025-05-12 12:36:11 |
| Message-ID: | CAKFQuwa96gN7P4Exi_iNVJv=CwWdVZ9ZRU=sn084GRyy-Bm=Hw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Monday, May 12, 2025, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18924
> Logged by: Adrien Ducos
> Email address: sysgeo(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-05-12 13:51:39 | Re: BUG #18923: pg_dump 18beta1 fails to process complex table names |
| Previous Message | PG Bug reporting form | 2025-05-12 09:51:21 | BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always |