From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: konstbozhko@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16980: invalid memory alloc request size
Date: Sat, 24 Apr 2021 10:54:08 -0400
Message-ID: <1661417.1619276048@sss.pgh.pa.us> (raw)
In-Reply-To: <YIOzqv+E5kJVJLr/@paquier.xyz>
References: <16980-0d2064db94c17318@postgresql.org>
<YIOzqv+E5kJVJLr/@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> On Fri, Apr 23, 2021 at 10:10:39AM +0000, PG Bug reporting form wrote:
>> I have a table attachment_contents in my PostgreSQL database with bytea type
>> column. One cell of this bytea column is too big (appr. 900Mb).
>> I receive error when try to select this cell:
>> taxmon=> select content from attachment_contents where attachment_id = 3293;
>> ERROR: invalid memory alloc request size 1850079891
>> How can i avoid this problem?
> No idea without more context. Some of your data may be corrupted,
> leading to this error. It may also be possible that you have
> discovered a new bug, but it is going to be hard for someone to figure
> out what's happening without a self-contained test case.
I doubt there's any corruption or unknown bug. If the bytea itself
is 900MB, its hex-string representation will be twice that, exceeding
the 1GB palloc chunk-size limit. So we can't represent the value as
text, and even if we could, it wouldn't fit into a DataRow message.
You can imagine various hacks that would move the threshold for
trouble, but the long and the short of it is that field values
exceeding maybe 100MB are likely to cause problems somewhere.
If you have to store such things, you'd be best off to keep them
in files outside the database.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, konstbozhko@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16980: invalid memory alloc request size
In-Reply-To: <1661417.1619276048@sss.pgh.pa.us>
* 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