Re: Fatal Error : Invalid Memory alloc request size 1236252631

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(at)gmail(dot)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(at)a-kretschmer(dot)de>
> wrote:
>
>>
>>
>> On 14 August 2023 11:59:26 CEST, Sai Teja <
>> saitejasaichintalapudi(at)gmail(dot)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
>>
>