Re: bytea_output output of base64

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: 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-25 23:59:30
Message-ID: 20170225235930.GA3439@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 25, 2017 at 06:49:01PM -0500, Peter Eisentraut wrote:
> On 2/23/17 17:55, Bruce Momjian wrote:
> > 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?
>
> The reason we changed from the old format to hex was for performance.
> We didn't consider base64 at the time, but hex would probably still have
> been faster.

OK, good to know. I was just asking.

--
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 +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2017-02-26 00:43:19 Re: snapbuild woes
Previous Message Peter Eisentraut 2017-02-25 23:49:01 Re: bytea_output output of base64