From: Noah Misch <noah@leadboat.com>
To: jitesh tiwari <jitesh120@gmail.com>
To: John Naylor <john.naylor@enterprisedb.com>
Cc: pgsql-bugs@postgresql.org
Subject: Re: fetching bytea (blob) data of 850 MB from psql client failed
Date: Wed, 31 Aug 2022 21:39:13 -0700
Message-ID: <20220901043913.GA1001056@rfd.leadboat.com> (raw)
In-Reply-To: <CAFBsxsExRqZjvkMNBLgS8D-5BUBG6JYhMsqngy=DB5cZOYBV=A@mail.gmail.com>
References: <CAOEdJKF4PFrHtH0OEn+Qmeqy-Z7UnNWUMAtrT+jVhTo3ozUjxw@mail.gmail.com>
<CAFBsxsExRqZjvkMNBLgS8D-5BUBG6JYhMsqngy=DB5cZOYBV=A@mail.gmail.com>
On Mon, Aug 22, 2022 at 05:52:29PM +0700, John Naylor wrote:
> If the data is binary and not printable ASCII, then there is no easy
> workaround.
I would say the chief solution is to request binary transmission in your
application. This cuts your network traffic in half for retrieving a bytea,
so it's a good change even if the server improves someday. If you're using
libpq, search for show_binary_results in
https://www.postgresql.org/docs/devel/libpq-example.html to see an example of
doing this. I don't know of an equivalent option in ODBC; if there is none,
one could modify the ODBC driver to use the same protocol feature that libpq
uses.
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: noah@leadboat.com, jitesh120@gmail.com, john.naylor@enterprisedb.com
Subject: Re: fetching bytea (blob) data of 850 MB from psql client failed
In-Reply-To: <20220901043913.GA1001056@rfd.leadboat.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