| From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
|---|---|
| To: | Rihad <grihad(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Collation again here |
| Date: | 2026-01-08 14:02:03 |
| Message-ID: | CAFCRh-_aDT9zgHRt-EyaaSuOonNCBny1RhJ57RS0g-uSP-rWFQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 8, 2026 at 2:18 PM Rihad <grihad(at)gmail(dot)com> wrote:
> We only have "i" & "c" in pg_collation. And we aren't using any of "i" it seems. All this locale/encoding/collate stuff is too much for me to handle, sorry)
As Daniel already told you, it's pg_database.datlocprovider that matters.
> So if we are using the internal (builtin) "c" provider how come the PG 18.1 run on FreeBSD 13.5 version shows warnings that the system version is 34.0?
"c" is NOT built-in. It's implemented thanks to the OS' libc as a dependency.
"b" is built-in, i.e. entirely within postgres, w/o external
dependencies (like icu or libc). New in PostgreSQL 18.
> Then upgrading (the OS from) 13.5 to 14.3 is our only option.
Given you're likely on "c", probably. As recommeded by Daniel. --DD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2026-01-08 16:04:56 | Re: Collation again here |
| Previous Message | Richard Guo | 2026-01-08 13:30:11 | Re: Fwd: pg18 bug? SELECT query doesn't work |