| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bytea_output output of base64 |
| Date: | 2017-02-23 22:55:37 |
| Message-ID: | 20170223225537.GP20486@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 23, 2017 at 04:08:58PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Is there a reason we don't support base64 as a bytea_output output
> > option, except that no one has implemented it?
>
> How about "we already have one too many bytea output formats"?
> I don't think forcing code to try to support still another one
> is a great thing ... especially not if it couldn't be reliably
> distinguished from the hex format.
Is there a reason we chose hex over base64?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkata B Nagothi | 2017-02-23 23:38:58 | Re: Range Partitioning behaviour - query |
| Previous Message | Tom Lane | 2017-02-23 22:28:26 | Re: Poor memory context performance in large hash joins |