Postgres Pro
Downloads
Home   >   mailing lists

Re: Fatal Error : Invalid Memory alloc request size 1236252631 - Mailing list pgsql-general

From Sai Teja
Subject Re: Fatal Error : Invalid Memory alloc request size 1236252631
Date
Msg-id CADBXDMU3J-ZcuCoRVaQGk9YufE=1wzZ4X1VEHFTvMXheiX8YTw@mail.gmail.com
Whole thread Raw
In response to Fatal Error : Invalid Memory alloc request size 1236252631  (Sai Teja <saitejasaichintalapudi@gmail.com>)
Responses Re: Fatal Error : Invalid Memory alloc request size 1236252631
List pgsql-general
Tree view
Could anyone please suggest any ideas to resolve this issue.

I have increased the below parameters but still I'm getting same error.

work_mem, shared_buffers

Out of 70k rows in the table only for the few rows which is of large size (700MB) getting the issue. Am unable to fetch the data for that particular row.

Would be appreciated if anyone share the insights.

Thanks,
Sai



On Mon, 14 Aug, 2023, 5:21 pm Sai Teja, <saitejasaichintalapudi@gmail.com> wrote:
Hi Andreas,

Thank you for the reply!

Currently it is Hex by default. If I change to escape is there any possibility to fetch the data?

Thanks,
Sai Teja

On Mon, 14 Aug, 2023, 5:12 pm Andreas Kretschmer, <andreas@a-kretschmer.de> wrote:


On 14 August 2023 11:59:26 CEST, Sai Teja <saitejasaichintalapudi@gmail.com> wrote:
>Hi Team,
>
>We are trying to fetch the one row of data (bytea data) for one table in
>But getting the error stating that "Invalid Memory alloc request size
>1236252631"
>
>The row which we were trying to fetch have one bytea column which is more
>than 1GB
>
>Could anyone please help me to resolve this issue.
>

You can try to change the bytea_output. Possible values are hex and escape. With some luck it will work, but maybe your application will have problems with that.

Andreas

pgsql-general by date:

Previous
From: David Gilman
Date:
Subject: Query plan regression between CTE and views
Next
From: Ron
Date:
Subject: Re: Query plan regression between CTE and views