MIME-Version: 1.0
References: <200eccb1-188e-49ee-9360-c3a7acb19c2c@gmail.com>
 <CAFCRh--H4a9kV4R=22DB6cL+KxcJ3A6-3tg_Y77KgTdDJECBwA@mail.gmail.com> <9f5996c1-abab-40da-8dd5-d56f483b22b1@gmail.com>
In-Reply-To: <9f5996c1-abab-40da-8dd5-d56f483b22b1@gmail.com>
From: Dominique Devienne <ddevienne@gmail.com>
Date: Thu, 8 Jan 2026 15:02:03 +0100
Message-ID: <CAFCRh-_aDT9zgHRt-EyaaSuOonNCBny1RhJ57RS0g-uSP-rWFQ@mail.gmail.com>
Subject: Re: Collation again here
To: Rihad <grihad@gmail.com>
Cc: pgsql-general General <pgsql-general@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAFCRh-_aDT9zgHRt-EyaaSuOonNCBny1RhJ57RS0g-uSP-rWFQ%40mail.gmail.com>
Precedence: bulk

On Thu, Jan 8, 2026 at 2:18=E2=80=AFPM Rihad <grihad@gmail.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 dependenc=
y.
"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