Collation changes

From: shammat(at)gmx(dot)net
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Collation changes
Date: 2026-05-30 19:41:56
Message-ID: e72cd1cf-d2e0-486a-af19-d865a545bcb7@gmx.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello,

I thought I had understood the problems with libc collation changes, but today a Fedora update showed me, that I probably did not :)

After refreshing the encodings for the databases (and reindexing) I thought I'd have a look at the versions in pg_collation using the following query:

select collname,
collversion,
pg_encoding_to_char(collencoding) as encoding,
pg_collation_actual_version(oid)
from pg_collation
where collprovider = 'c'
and collversion <> pg_collation_actual_version(oid)

The query returned several hundred collations, all with a non UTF-8 encoding (mostly single byte encodings).

Running "alter collation ... refresh version" on them resulted in

NOTICE: version has not changed

Which confuses me, as the above query showed collversion = 2.41 and pg_collation_actual_version() returned 2.43

Can someone clear up my confusion?

Browse pgsql-admin by date

  From Date Subject
Next Message Ramakrishna Reddy Nandyala 2026-06-03 12:14:39 Any known bugs with respect to data corruption in pg12/pg 14
Previous Message Laurenz Albe 2026-05-26 07:57:26 Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment