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

From: Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>
To: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Implementing full UTF-8 support (aka supporting 0x00)
Date: 2016-08-03 18:15:44
Message-ID: 13c36522-ca3f-5e78-3518-6615f3defb7f@8kdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/08/16 18:35, Geoff Winkless wrote:
> On 3 August 2016 at 15:54, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> wrote:
>> Given that 0x00 is a perfectly legal UTF-8 character, I conclude we're
>> strictly non-compliant.
> It's perhaps worth mentioning that 0x00 is valid ASCII too, and
> PostgreSQL has never stored that either.

Then yes, it could also be a problem. But as of today I believe
solving the problem for UTF-8 would solve the great majority of this
embedded NUL problems.

Álvaro

--

Álvaro Hernández Tortosa

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2016-08-03 18:23:28 Re: Optimizing numeric SUM() aggregate
Previous Message Tom Lane 2016-08-03 18:15:18 Re: New version numbering practices