Aw: Re: Fatal Error : Invalid Memory alloc request size 1236252631

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: Sai Teja <saitejasaichintalapudi(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Aw: Re: Fatal Error : Invalid Memory alloc request size 1236252631
Date: 2023-08-17 14:35:32
Message-ID: trinity-52d1c07e-0519-414d-817e-70638bf7986d-1692282932894@3c-app-gmx-bs52
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

 
Even I used postgreSQL Large Objects by referring this link to store and retrieve large files (As bytea not working)
https://www.postgresql.org/docs/current/largeobjects.html
 
But even now I am unable to fetch the data at once from large objects
 
select lo_get(oid);
 
Here I'm getting the same error message.
 
But if I use select data from pg_large_object where loid = 49374
Then I can fetch the data but in page wise (data splitting into rows of each size 2KB)
 
So, here how can I fetch the data at single step rather than page by page without any error.
 
And I'm just wondering how do many applications storing huge amount of data in GBs? I know that there is 1GB limit for each field set by postgreSQL. If so, how to deal with these kind of situations? Would like to know about this to deal with real time scenarios.

https://github.com/lzlabs/pg_dumpbinary/blob/master/README.md
might be of help

Karsten

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2023-08-17 14:36:20 Re: Base files compatibility between PG11 and PG15
Previous Message Erik Wienhold 2023-08-17 13:37:21 Re: AW: AW: Cast INTEGER to BIT confusion