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 ebf0ed5e-67c0-4f63-3407-5b4592e0f7c3@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] bytea_output output of base64  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [HACKERS] bytea_output output of base64  (Bruce Momjian <bruce@momjian.us>)
Re: [HACKERS] bytea_output output of base64  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
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@momjian.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.

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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] bytea_output output of base64