| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: glibc updarte 2.31 to 2.38 |
| Date: | 2024-09-22 16:52:30 |
| Message-ID: | 7B4B80AE-C541-4A4C-A3AA-DD1B4027C171@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Ron,
> On 22. Sep, 2024, at 16:11, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
>
> The real question is why nobody notices it in other RDBMSs like Oracle, SQL Server and MySQL.
The answer is simple for Oracle: It includes a whole zoo of locale mappings and uses each one as it is needed. This is one of the many things with Oracle that only grows over time but does never get smaller again.
I suspect it's similar with MariaDB, MySQL, SQL Server and others. Only PostgreSQL has no such thing as a local inventory and relies on either glibc or ICU.
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-09-22 16:53:58 | Re: glibc updarte 2.31 to 2.38 |
| Previous Message | Paul Förster | 2024-09-22 16:48:46 | Re: glibc updarte 2.31 to 2.38 |