pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: pgsql-general@lists.postgresql.org
Subject: Re: Q: error on updating collation version information
Date: Sun, 4 Dec 2022 10:09:47 -0800
Message-ID: <954702a5-3552-640e-6df9-a03ab5fbc339@aklaver.com> (raw)
In-Reply-To: <Y4yUCqaXM5IOiyLM@hermes.hilbert.loc>
References: <Y4yQ6pJuuCQ1w1xI@hermes.hilbert.loc>
	<Y4yUCqaXM5IOiyLM@hermes.hilbert.loc>

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






view thread (7+ messages)  latest in thread

Message-ID: <954702a5-3552-640e-6df9-a03ab5fbc339@aklaver.com>
Permalink:  ../954702a5-3552-640e-6df9-a03ab5fbc339@aklaver.com/
Also on:    postgresql.org/message-id/954702a5-3552-640e-6df9-a03ab5fbc339@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, Karsten.Hilbert@gmx.net
  Subject: Re: Q: error on updating collation version information
  In-Reply-To: <954702a5-3552-640e-6df9-a03ab5fbc339@aklaver.com>
  References: <Y4yQ6pJuuCQ1w1xI@hermes.hilbert.loc> <Y4yUCqaXM5IOiyLM@hermes.hilbert.loc> <954702a5-3552-640e-6df9-a03ab5fbc339@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox