Re: Implementing full UTF-8 support (aka supporting 0x00)

From: Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>
To: Kevin Grittner <kgrittn(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Implementing full UTF-8 support (aka supporting 0x00)
Date: 2016-08-03 18:14:04
Message-ID: ca3608a6-8fad-67de-d368-a52318aed3d7@8kdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/08/16 17:47, Kevin Grittner wrote:
> On Wed, Aug 3, 2016 at 9:54 AM, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> wrote:
>
>> What would it take to support it?
> Would it be of any value to support "Modified UTF-8"?
>
> https://en.wikipedia.org/wiki/UTF-8#Modified_UTF-8
>

That's nice, but I don't think so.

The problem is that you cannot predict how people would send you
data, like when importing from other databases. I guess it may work if
Postgres would implement such UTF-8 variant and also the drivers, but
that would still require an encoding conversion (i.e., parsing every
string) to change the 0x00, which seems like a serious performance hit.

It could be worse than nothing, though!

Thanks,

Álvaro

--

Álvaro Hernández Tortosa

-----------
8Kdata

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-08-03 18:15:18 Re: New version numbering practices
Previous Message Robert Haas 2016-08-03 18:12:30 Re: Why we lost Uber as a user