Re: [HACKERS] bytea_output output of base64 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] bytea_output output of base64
Date
Msg-id ba797640-f145-c3f0-1d32-93e316826852@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] bytea_output output of base64  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] bytea_output output of base64
List pgsql-hackers
On 2/26/17 05:05, Robert Haas wrote:
> That having been said, I do agree with Tom's point that we already
> have one more bytea_output format than would be ideal.  To justify
> implementing base64 as a third choice, it would have to not only be
> better than hex, but enough better to justify the migration pain.  I'm
> not sure whether it could clear that bar.

Another point is that an "output" format is not the same as an
"encoding" format.  An output format should be somewhat human-readable.
Otherwise we could find all kinds of more compact output formats for
different data types.  The hex format satisfies all of performance, ease
of use, and readability pretty well, I think.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker)
Date:
Subject: Re: [HACKERS] [PATCH] Add GUCs for predicate lock promotion thresholds
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] WIP: Covering + unique indexes.