Re: Strangeness with UNIQUE indexes and UTF-8

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Omar Kilani <omar(dot)kilani(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Strangeness with UNIQUE indexes and UTF-8
Date: 2021-06-06 15:08:27
Message-ID: 634925.1622992107@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Omar Kilani <omar(dot)kilani(at)gmail(dot)com> writes:
> This is a very old database (2004) that has moved forward via pg_upgrade. I
> think we did a pg_dump and pg_restore every time we hit some major
> incompatibility like float vs integer date times.

If it's that old, it's likely also survived multiple OS upgrades.
It seems clear that this index has been corrupt for awhile, and
I'm wondering whether the corruption was brought on by an OS
locale change. There's useful info at

https://wiki.postgresql.org/wiki/Locale_data_changes

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Omar Kilani 2021-06-06 15:08:51 Re: Strangeness with UNIQUE indexes and UTF-8
Previous Message Tom Lane 2021-06-06 14:37:58 Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch