From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrey Klychkov <aaklychkov@mail.ru>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Re[2]:
Date: Tue, 26 May 2020 10:50:19 -0400
Message-ID: <17907.1590504619@sss.pgh.pa.us> (raw)
In-Reply-To: <1590501239.839686286@f437.i.mail.ru>
References: <1590486572.205117372@f500.i.mail.ru>
<cca87255-7dea-6aac-2e9a-35dfe3776122@2ndquadrant.com>
<1590501239.839686286@f437.i.mail.ru>
=?UTF-8?B?QW5kcmV5IEtseWNoa292?= <aaklychkov@mail.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, aaklychkov@mail.ru, peter.eisentraut@2ndquadrant.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Re[2]:
In-Reply-To: <17907.1590504619@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox