Re: String comparison fails for some cases after migration

From: Jayadevan M <maymala(dot)jayadevan(at)gmail(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: String comparison fails for some cases after migration
Date: 2021-10-27 10:48:38
Message-ID: CAFS1N4jCt0ZMgEoF=68KJMwWYS6PgS9Ftdnug6zuypSF1LpktQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Oct 27, 2021 at 11:49 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:

>
>
> Most likely you had a different version of the glibc or ICU libraries
> on the new system, which lead to your indexes on collatable datatypes
> partially corrupted. See https://wiki.postgresql.org/wiki/Collations
> for more details.
>
> You can issue a REINDEX for each impacted index, or a database-wide
> REINDEX.
>

Tried creating a new env with the same approach - just reindexing solved
the problem. Thanks a lot.

Regards,
Jayadevan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marcos Pegoraro 2021-10-27 10:56:20 Re: Determining if a table really changed in a trigger
Previous Message Thomas Kellerer 2021-10-27 08:02:27 Re: Determining if a table really changed in a trigger