| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jorel Casal <jcasal(at)ixl(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Corrupt Index |
| Date: | 2022-03-15 16:41:35 |
| Message-ID: | 328626.1647362495@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jorel Casal <jcasal(at)ixl(dot)com> writes:
> During a Patroni leader switchover, we had a situation where a unique index
> stopped "working", the index did not have records
> that were in fact in the table and the table had duplicate records which
> should have been prevented by said unique index.
If the index was on a string type (text/varchar), the most likely
explanation is a switch to a different OS version with inconsistent
collation rules. See
https://wiki.postgresql.org/wiki/Locale_data_changes
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2022-03-15 17:40:49 | Re: [External]Re: Postgres Crash Issue |
| Previous Message | Jorel Casal | 2022-03-15 16:01:05 | Corrupt Index |