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

From: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
To: Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>
Cc: Kevin Grittner <kgrittn(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Implementing full UTF-8 support (aka supporting 0x00)
Date: 2016-08-03 19:31:49
Message-ID: CAEzk6fd89ddBdaw6mJJgo+G-NHKQX75VGh+Ssq5dq9SsOVbrMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3 August 2016 at 20:13, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> wrote:
> Yet they are accepted by Postgres
> (like if Postgres would support Modified UTF-8 intentionally). The caracter
> in psql does not render as a nul but as this symbol: "삀".

Not accepted as valid utf8:

# select E'\xc0\x80';
ERROR: invalid byte sequence for encoding "UTF8": 0xc0 0x80

You would need a "modified utf8" encoding, I think.

Geoff

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Hernández Tortosa 2016-08-03 19:36:26 Re: Implementing full UTF-8 support (aka supporting 0x00)
Previous Message Tom Lane 2016-08-03 19:15:54 Re: Why we lost Uber as a user