| From: | Phil Krylov <phil(at)krylov(dot)eu> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Nico Williams <nico(at)cryptonector(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Pre-proposal: unicode normalized text |
| Date: | 2023-11-03 20:15:30 |
| Message-ID: | b5ad7935d2c0d53a361b2fe0efc8b0c6@krylov.eu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Jones | 2023-11-03 20:28:21 | Re: [PATCH] Add XMLText function (SQL/XML X038) |
| Previous Message | Robert Haas | 2023-11-03 19:50:51 | Re: trying again to get incremental backup |