From: Colin Beckingham <colbec@kingston.net>
To: pgsql-admin@lists.postgresql.org
Subject: Bytea data in SQL output pane
Date: Wed, 27 Jun 2018 10:40:44 -0400
Message-ID: <d35000f0-e2a2-eb0b-1a67-0d62669ee20f@kingston.net> (raw)
Currently any bytea fields are rendered as "[binary data]" in SQL output
pane. From the archive I found a message that evidently there was very
high processor load in trying to show the data. I guess the solution at
the time was not to render the data at all. Bytea is used a lot in
crypto, an example is blockchain hashes. It is handy to be able to see
that hashes end up in the right record and right column. A workaround is
to use pgphpadmin which reveals the correct codes, and as long as we use
the now (Postgresql 10) non-default 'escape' encoding and not the
default 'hex' the data is visible in the REPL as well. Just wondering
where this issue sits in the TODO list if any?
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-admin@postgresql.org
Cc: colbec@kingston.net, pgsql-admin@lists.postgresql.org
Subject: Re: Bytea data in SQL output pane
In-Reply-To: <d35000f0-e2a2-eb0b-1a67-0d62669ee20f@kingston.net>
* 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