Re: BUG #16593: pg_upgrade make corrupt UK indexes - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: BUG #16593: pg_upgrade make corrupt UK indexes
Date
Msg-id CABUevEyf1yShkWOHyZwbxpLAh4hYigBzQqs_Nc+k58mquZ5M2w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16593: pg_upgrade make corrupt UK indexes  (Nick Cleaton <nick@cleaton.net>)
Responses Re: BUG #16593: pg_upgrade make corrupt UK indexes  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs


On Wed, Aug 26, 2020 at 7:38 AM Nick Cleaton <nick@cleaton.net> wrote:
On Tue, 25 Aug 2020 at 23:55, PG Bug reporting form <noreply@postgresql.org> wrote:
We upgrade from 9.6 Centos7 to 12.3 Centos 8


> Comparisons of datums of a collatable type like text must be immutable (just as all comparisons used for B-Tree index scans must be immutable), which implies that operating system collation rules must never change. Though rare, updates to operating system collation rules can cause these issues. More commonly, an inconsistency in the collation order between a master server and a standby server is implicated, possibly because the major operating system version in use is inconsistent

And in particular also see https://wiki.postgresql.org/wiki/Locale_data_changes, which shows that the step from Centos7 to Centos8 is one that causes this problem. You need to reindex all text/varchar indexes when you  make that upgrade.

--

pgsql-bugs by date:

Previous
From: Nick Cleaton
Date:
Subject: Re: BUG #16593: pg_upgrade make corrupt UK indexes
Next
From: Robins Tharakan
Date:
Subject: Re: ALTER TABLE ALTER COLUMN SET TYPE crash