Collation changes - Mailing list pgsql-admin

From shammat@gmx.net
Subject Collation changes
Date
Msg-id e72cd1cf-d2e0-486a-af19-d865a545bcb7@gmx.net
Whole thread
List pgsql-admin
Hello,

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

After refreshing the encodings for the databases (and reindexing) I thought I'd have a look at the versions in
pg_collationusing 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?




pgsql-admin by date:

Previous
From: mahamood hussain
Date:
Subject: Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment
Next
From: Ramakrishna Reddy Nandyala
Date:
Subject: Any known bugs with respect to data corruption in pg12/pg 14