From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Fatal Error : Invalid Memory alloc request size 1236252631
Date: Mon, 14 Aug 2023 14:14:18 -0500
Message-ID: <fc1a13d5-3c9a-8480-94f9-0f20446d1e43@gmail.com> (raw)
In-Reply-To: <CADBXDMUsV948B06XwLamQ5PFhDO-fZEz3Bi9fPNzaEOP4sLiDg@mail.gmail.com>
References: <CADBXDMXVtbyHbqMD73P2tX54u55XewvYLt+a+VEsyzrtQuo6jA@mail.gmail.com>
<6BDA46BE-B926-4BF7-AEBF-C9153D59A51D@a-kretschmer.de>
<CADBXDMWBR1jWXioyBOX60UTTOecyPEJ6Mb0-yR5C5r8ZrwF50A@mail.gmail.com>
<CADBXDMU3J-ZcuCoRVaQGk9YufE=1wzZ4X1VEHFTvMXheiX8YTw@mail.gmail.com>
<a110e3f6-4cf1-1706-9604-c3f20afd1082@gmail.com>
<CADBXDMUsV948B06XwLamQ5PFhDO-fZEz3Bi9fPNzaEOP4sLiDg@mail.gmail.com>
Did you /try/ changing bytea_output to hex?
On 8/14/23 12:31, Sai Teja wrote:
> I am just running select query to fetch the result
> Query : select id, content_data, name from table_name
> So here content_data is bytea content which is having more than 700 MB.
> Even if I run this query in any DB client such as Pgadmin, dbeaver etc..
> I'm facing the same error. But this query is being called in java as well
> So, I don't think java could be the issue as I can able to successfully
> insert the data. But, only the problem is with fetching the data that too
> only specific rows which are having huge volume of data.
>
> Thanks,
> Sai
>
> On Mon, 14 Aug, 2023, 10:55 pm Rob Sargent, <robjsargent@gmail.com> wrote:
>
> On 8/14/23 09:29, Sai Teja wrote:
> > 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
> >
> >
> Are you using java? There's an upper limit on array size, hence also on
> String length. You'll likely need to process the output in chunks.
>
>
--
Born in Arizona, moved to Babylonia.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: Fatal Error : Invalid Memory alloc request size 1236252631
In-Reply-To: <fc1a13d5-3c9a-8480-94f9-0f20446d1e43@gmail.com>
References: <CADBXDMXVtbyHbqMD73P2tX54u55XewvYLt+a+VEsyzrtQuo6jA@mail.gmail.com> <6BDA46BE-B926-4BF7-AEBF-C9153D59A51D@a-kretschmer.de> <CADBXDMWBR1jWXioyBOX60UTTOecyPEJ6Mb0-yR5C5r8ZrwF50A@mail.gmail.com> <CADBXDMU3J-ZcuCoRVaQGk9YufE=1wzZ4X1VEHFTvMXheiX8YTw@mail.gmail.com> <a110e3f6-4cf1-1706-9604-c3f20afd1082@gmail.com> <CADBXDMUsV948B06XwLamQ5PFhDO-fZEz3Bi9fPNzaEOP4sLiDg@mail.gmail.com> <fc1a13d5-3c9a-8480-94f9-0f20446d1e43@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox