Message-ID: <573029acb7dd0956fb5334c3a3b71ffee16b4c0d.camel@j-davis.com>
Subject: Re: Pre-proposal: unicode normalized text
From: Jeff Davis <pgsql@j-davis.com>
To: Nico Williams <nico@cryptonector.com>
Cc: Chapman Flack <chap@anastigmatix.net>, Robert Haas
 <robertmhaas@gmail.com>,  pgsql-hackers@postgresql.org
Date: Wed, 04 Oct 2023 16:01:26 -0700
In-Reply-To: <ZR3V2vmpfxnDw3Q0@ubby21>
References: <f30b58657ceb71d5be032decf4058d454cc1df74.camel@j-davis.com>
	 <ZR2fnTPDwPb0IamC@ubby21>
	 <CA+TgmoY6vNbDoBugDT=3rdJ-diyLw-kQ9sxB2JXenv48xV_tVQ@mail.gmail.com>
	 <43864caecd65d02081d623d05ccc1683@anastigmatix.net>
	 <a415e27830b8c94cea1b1c4bd60d254f0f397866.camel@j-davis.com>
	 <ZR3V2vmpfxnDw3Q0@ubby21>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu2 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/573029acb7dd0956fb5334c3a3b71ffee16b4c0d.camel%40j-davis.com>
Precedence: bulk

On Wed, 2023-10-04 at 16:15 -0500, Nico Williams wrote:
> Better that than TEXT blobs w/ the encoding given by the `CREATE
> DATABASE` or `initdb` default!

From an engineering perspective, yes, per-column encodings would be
more flexible. But I still don't understand who exactly would use that,
and why.

It would take an awful lot of effort to implement and make the code
more complex, so we'd really need to see some serious demand for that.

Regards,
	Jeff Davis