| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrey Klychkov <aaklychkov(at)mail(dot)ru> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Re[2]: |
| Date: | 2020-05-26 14:50:19 |
| Message-ID: | 17907.1590504619@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?UTF-8?B?QW5kcmV5IEtseWNoa292?= <aaklychkov(at)mail(dot)ru> writes:
>> Did you by any chance upgrade the operating system on this server at
>> some point?
> It was installed from Centos 8.1 official iso, then was updated right after installation.
Well, there are two issues here:
1. How did you manage to get duplicate entries into the table? This
suggests that the existing index is corrupt, else it should have detected
the duplicate. Peter's question was leading towards one known way that
indexes on text columns can become corrupt.
2. Is reindexdb handling the failure sanely? While I'd agree that
this behavior isn't especially desirable, it's the price of using
REINDEX CONCURRENTLY. On failure, you're expected to clean up
manually by removing the leftover invalid index. Perhaps the
documentation isn't clear enough about that, but I don't see a
bug there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2020-05-26 17:00:38 | BUG #16464: Unable to restore database backed up with pg_dump into sql that contains expression based index |
| Previous Message | Tom Lane | 2020-05-26 13:55:42 | Re: BUG #16463: Sporadic SSL handshake failures in Windows client |