| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | "Thompson, Shon" <Shon(dot)Thompson(at)MaineGeneral(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: <EXTERNAL> Re: Invalid memory alloc querying field type bytea |
| Date: | 2020-07-09 14:23:36 |
| Message-ID: | a9e2d6a1-5476-889a-7a4a-89462efe9a1b@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 7/8/20 11:25 AM, Thompson, Shon wrote:
> Postgres returns the smaller rows without errors, but cannot return the two
> largest bytea fields. The length function for the bytea data of these two
> rows returns:
> 647,034,150
> 819,319,303
>> "ERROR: XX000: invalid memory alloc request size 1294068297"
The problem is probably byteaout rendering the bytes as (presumably) hex, which
takes ~twice as many bytes as the data, and runs afoul of MaxAllocSize.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2020-07-09 15:55:29 | Re: BUG #16529: Installation error/bug |
| Previous Message | Amit Langote | 2020-07-09 07:16:15 | Re: posgres 12 bug (partitioned table) |