Re: BUG #16593: pg_upgrade make corrupt UK indexes

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Nick Cleaton <nick(at)cleaton(dot)net>
Cc: hali19790320(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16593: pg_upgrade make corrupt UK indexes
Date: 2020-08-26 07:49:00
Message-ID: CABUevEyf1yShkWOHyZwbxpLAh4hYigBzQqs_Nc+k58mquZ5M2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Aug 26, 2020 at 7:38 AM Nick Cleaton <nick(at)cleaton(dot)net> wrote:

> On Tue, 25 Aug 2020 at 23:55, PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>
>> We upgrade from 9.6 Centos7 to 12.3 Centos 8
>>
>
> This from https://www.postgresql.org/docs/12/amcheck.html#id-1.11.7.11.9
> might be relevent:
>
> > 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.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robins Tharakan 2020-08-26 10:57:22 Re: ALTER TABLE ALTER COLUMN SET TYPE crash
Previous Message Michael Paquier 2020-08-26 07:30:01 Re: ALTER TABLE ALTER COLUMN SET TYPE crash