From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | haduchiep(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17932: Cannot select big bytea values(>500MB) |
Date: | 2023-05-16 01:58:47 |
Message-ID: | CAFBsxsFZ+NDhuyj8aAOpXzyuDq_ZU6XB6h8oGumjJ8DgLyb1=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, May 15, 2023 at 5:21 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> I created a big bytea value and try to select it from a table, I get
> an error, something like: "ERROR: invalid memory alloc request size
> ...".
> it means i can insert data into table but then i can't even work
> with it. is it a bug? could you please help me to solve this Problem.
> Thank you very much for your support
This is a known (but not documented as far as I know) issue, but it also
depends on the data contents and how the value is retrieved. Possible
workarounds:
1. If the data is largely printable ASCII, then try
setting "bytea_output" to "escape":
https://www.postgresql.org/docs/devel/runtime-config-client.html#GUC-BYTEA-OUTPUT
2. Request binary transmission in your application (if possible), for
example "show_binary_results" in
https://www.postgresql.org/docs/devel/libpq-example.html
3. COPY out using binary format
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Manika Singhal | 2023-05-16 06:22:35 | Re: BUG #17931: Faild to stop PostgresSQL Service |
Previous Message | Tom Lane | 2023-05-16 00:03:16 | Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware) |