Re: Q: error on updating collation version information

On 12/4/22 04:35, Karsten Hilbert wrote:
> Am Sun, Dec 04, 2022 at 01:22:02PM +0100 schrieb Karsten Hilbert:
> 
>> following an ICU upgrade, collations in a stock Debian PG 15.1
>> cluster now have divergent version information in pg_collations.
> 
> Correction: this is following a libc upgrade 2.35 -> 2.36

So to be clear this database is not using ICU, but collations from libc?

How was the database installed?

In first post you had:

gnumed_v22=> select *, pg_encoding_to_char(collencoding) from 
pg_collation where collname = 'br_FR@euro';
    -[ RECORD 1 ]-------+-----------
    oid                 | 12413
    collname            | br_FR@euro
    collnamespace       | 11
    collowner           | 10
    collprovider        | c
    collisdeterministic | t
    collencoding        | 16
    collcollate         | br_FR@euro
    collctype           | br_FR@euro
    colliculocale       |
    collversion         | 2.35
    pg_encoding_to_char | LATIN9

where collprovider c means libc and collversion 2.35.

Not exactly sure how that interacts with from here:

https://www.postgresql.org/docs/current/catalog-pg-collation.html

collversion text

Provider-specific version of the collation. This is recorded when the 
collation is created and then checked when it is used, to detect changes 
in the collation definition that could lead to data corruption.

> 
> Karsten
> --
> GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com