Re: [HACKERS] bytea_output output of base64
От | David Fetter |
---|---|
Тема | Re: [HACKERS] bytea_output output of base64 |
Дата | |
Msg-id | 20170223235246.GA15217@fetter.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] bytea_output output of base64 (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: [HACKERS] bytea_output output of base64
Re: [HACKERS] bytea_output output of base64 Re: [HACKERS] bytea_output output of base64 |
Список | pgsql-hackers |
On Thu, Feb 23, 2017 at 05:55:37PM -0500, 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? Whether there was or not, there's not a compelling reason now to break people's software. When people want compression, methods a LOT more effective than base64 are common. Gzip, for example. Best, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
В списке pgsql-hackers по дате отправления: