Horton

Re: Pre-proposal: unicode normalized text

Phil Krylov <phil@krylov.eu>

View thread
From: Phil Krylov <phil@krylov.eu>
To: Chapman Flack <chap@anastigmatix.net>
Cc: Jeff Davis <pgsql@j-davis.com>, Robert Haas <robertmhaas@gmail.com>, Nico Williams <nico@cryptonector.com>, pgsql-hackers@postgresql.org
Date: 2023-11-03T20:15:30Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Try again to fix the MSVC build

  2. Additional unicode primitive functions.

On 2023-10-04 23:32, Chapman Flack wrote:
> Well, for what reason does anybody run PG now with the encoding set
> to anything besides UTF-8? I don't really have my finger on that pulse.
> Could it be that it bloats common strings in their local script, and
> with enough of those to store, it could matter to use the local
> encoding that stores them more economically?

I do use CP1251 for storing some data which is coming in as XMLs in 
CP1251, and thus definitely fits. In UTF-8, that data would take exactly 
2x the size on disks (before compression, and pglz/lz4 won't help much 
with that).

-- Ph.