Date: Wed, 31 Aug 2022 21:39:13 -0700
From: Noah Misch <noah@leadboat.com>
To: jitesh tiwari <jitesh120@gmail.com>,
	John Naylor <john.naylor@enterprisedb.com>
Cc: pgsql-bugs@postgresql.org
Subject: Re: fetching bytea (blob) data of 850 MB from psql client failed
Message-ID: <20220901043913.GA1001056@rfd.leadboat.com>
References: 
 <CAOEdJKF4PFrHtH0OEn+Qmeqy-Z7UnNWUMAtrT+jVhTo3ozUjxw@mail.gmail.com>
 <CAFBsxsExRqZjvkMNBLgS8D-5BUBG6JYhMsqngy=DB5cZOYBV=A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAFBsxsExRqZjvkMNBLgS8D-5BUBG6JYhMsqngy=DB5cZOYBV=A@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: 
 <https://www.postgresql.org/message-id/20220901043913.GA1001056%40rfd.leadboat.com>
Precedence: bulk

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.