| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bytea_output output of base64 |
| Date: | 2017-02-27 13:38:04 |
| Message-ID: | ba797640-f145-c3f0-1d32-93e316826852@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-02-27 13:40:26 | Re: WIP: Covering + unique indexes. |
| Previous Message | Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= | 2017-02-27 13:35:32 | Re: [PATCH] Add GUCs for predicate lock promotion thresholds |