From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nico Williams <nico@cryptonector.com>
cc: Robert Haas <robertmhaas@gmail.com>,
        Isaac Morland <isaac.morland@gmail.com>,
        Jeff Davis <pgsql@j-davis.com>, Chapman Flack <chap@anastigmatix.net>,
        pgsql-hackers@postgresql.org
Subject: Re: Pre-proposal: unicode normalized text
In-reply-to: <ZR8LLrk9AJVxEFbX@ubby21>
References: <f30b58657ceb71d5be032decf4058d454cc1df74.camel@j-davis.com>
 <ZR2fnTPDwPb0IamC@ubby21>
 <CA+TgmoY6vNbDoBugDT=3rdJ-diyLw-kQ9sxB2JXenv48xV_tVQ@mail.gmail.com>
 <43864caecd65d02081d623d05ccc1683@anastigmatix.net>
 <CAMsGm5eyegAkb2Eq+8d2j+BxDnSZXH0AUciwi6rA60V_ft=1dw@mail.gmail.com>
 <94a0e631b787d56fec1b17e03fe045b5e14907c1.camel@j-davis.com>
 <CAMsGm5f8k4_C6VuerSbF2gXeVwD9kMZQk43kO85Oi4oGVL7EMA@mail.gmail.com>
 <CA+TgmobAxizsgjxvZdEQxjEs6RA3qu7JLti_LdXtaXODJoWzNw@mail.gmail.com>
 <ZR8LLrk9AJVxEFbX@ubby21>
Comments: In-reply-to Nico Williams <nico@cryptonector.com>
	message dated "Thu, 05 Oct 2023 14:14:54 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2816607.1696535377.1@sss.pgh.pa.us>
Date: Thu, 05 Oct 2023 15:49:37 -0400
Message-ID: <2816608.1696535377@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2816608.1696535377%40sss.pgh.pa.us>
Precedence: bulk

Nico Williams <nico@cryptonector.com> writes:
> Text+encoding can be just like bytea with a one- or two-byte prefix
> indicating what codeset+encoding it's in.  That'd be how to encode
> such text values on the wire, though on disk the column's type should
> indicate the codeset+encoding, so no need to add a prefix to the value.

The precedent of BOMs (byte order marks) suggests strongly that
such a solution would be horrible to use.

			regards, tom lane