2.7.0.beta2 upgrade failed with ERROR: duplicate key

[omarfilip]

@Gunnar

find them and fix them all before I try again

A less invasive approach may be to reindex the database before upgrading and should tell you which ones need to be fixed.

Corrupt indexes in PG12, how do I fix?

Sorry for bumping this once again, I got a very strange discourse=# REINDEX SCHEMA CONCURRENTLY public; ERROR: could not create unique index "index_tags_on_name_ccnew" DETAIL: Key (name)=(chronicillness) is duplicated. I’m assuming it can be fixed by the solution suggested above by @riking but I’m unable to figure out how to modify the syntax to suit my case.