Currently pgadmin4 displays bytea fields as "[Binary Data]".
In searching the archives for the reason for this, I found some
discussion on lengthy processing slowing down display. So a decision was
made to not attempt to display the data at all, and since the data can
be lengthy this makes some sense.
While such binary data is not "readable", in the era of SHA hashes it is
useful to be able to visually check that the right hash is in the right
column using the first few text characters. We can of course do this in
the Postgresql REPL or even in the old phpPgAdmin which usefully
displays part of the 'escape' translation of the hash.
Is there some concrete reason for not displaying such data, or is the
community open to revealing a short stub which would be more helpful
than no representation at all? Thanks.
