pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Re: 2+ messages / 2 participants [nested] [flat]
* Re: @ 2020-06-08 17:37 Alvaro Herrera <alvherre@2ndquadrant.com> 2020-06-09 01:36 ` Re: Michael Paquier <michael@paquier.xyz> 0 siblings, 1 reply; 2+ messages in thread From: Alvaro Herrera @ 2020-06-08 17:37 UTC (permalink / raw) To: Andrey Klychkov <aaklychkov@mail.ru>; +Cc: Michael Paquier <michael@paquier.xyz>; Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; pgsql-bugs@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us> On 2020-May-27, Andrey Klychkov wrote: > ======= > BEFORE: > ======= > > Indexes: > "act_re_procdef_pkey" PRIMARY KEY, btree (id_) > "act_uniq_procdef" UNIQUE CONSTRAINT, btree (key_, version_, tenant_id_) > "act_re_procdef_deployment_id_idx" btree (deployment_id_) > ===== > AFTER > ===== > > Indexes: > "act_re_procdef_pkey" PRIMARY KEY, btree (id_) > "act_re_procdef_pkey_ccnew" UNIQUE, btree (id_) INVALID > "act_uniq_procdef" UNIQUE CONSTRAINT, btree (key_, version_, tenant_id_) > "act_uniq_procdef_ccnew" UNIQUE, btree (key_, version_, tenant_id_) INVALID > "act_re_procdef_deployment_id_idx" btree (deployment_id_) > "act_re_procdef_deployment_id_idx_ccnew" btree (deployment_id_) INVALID > I got the error related to the one UNIQUE index, why all the new indexes are invalid? > >There is a paragraph about the handling of invalid indexes on the > >reindex page: > >https://www.postgresql.org/docs/devel/sql-reindex.html#SQL-REINDEX-CONCURRENTLY > >"The recommended recovery method in such cases is to drop the invalid > >index and try again to perform REINDEX CONCURRENTLY. I think this part remains unanswered: why are there *three* invalid indexes, and not two? It makes sense for the UNIQUE indexes to acquire invalid duplicates, but strangely we also have a act_re_procdef_deployment_id_idx_ccnew which is *not* unique. What happened there? (I also wonder if it wouldn't make more sense to reindexdb to attempt to drop indexes that it couldn't complete.) -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: 2020-06-08 17:37 Re: Alvaro Herrera <alvherre@2ndquadrant.com> @ 2020-06-09 01:36 ` Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 2+ messages in thread From: Michael Paquier @ 2020-06-09 01:36 UTC (permalink / raw) To: Alvaro Herrera <alvherre@2ndquadrant.com>; +Cc: Andrey Klychkov <aaklychkov@mail.ru>; Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; pgsql-bugs@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us> On Mon, Jun 08, 2020 at 01:37:07PM -0400, Alvaro Herrera wrote: > I think this part remains unanswered: why are there *three* invalid > indexes, and not two? It makes sense for the UNIQUE indexes to acquire > invalid duplicates, but strangely we also have a > act_re_procdef_deployment_id_idx_ccnew which is *not* unique. What > happened there? More than one REINDEX query at table-level failed I guess? > (I also wonder if it wouldn't make more sense to reindexdb to attempt to > drop indexes that it couldn't complete.) (That's a good idea.) -- Michael Attachments: signature.asc (application/pgp-signature, 832B) download ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2020-06-09 01:36 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2020-06-08 17:37 Re: Alvaro Herrera <alvherre@2ndquadrant.com> 2020-06-09 01:36 ` Michael Paquier <michael@paquier.xyz>
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