Getting this error during restore: `could not create unique index`

[IdentityDan (Dan Woda)]

Howdy,

I am trying to get my staging instance up to date with my production instance. I successfully upgraded to the current version, but am receiving the following error while trying to restore my prod backup to my staging instance:

[2020-01-14 23:27:08] ERROR:  could not create unique index "index_tags_on_lower_name"
[2020-01-14 23:27:08] DETAIL:  Key (lower(name::text))=(net) is duplicated.
[2020-01-14 23:27:08] EXCEPTION: psql failed: DETAIL:  Key (lower(name::text))=(net) is duplicated.

I found this topic which seems similar, but don’t know how to implement the solution.

Add Tags 500 Error

Hi, I just add Tags, 500 Error. logs: ActiveRecord::RecordNotUnique (PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_tags_on_name" DETAIL: Key (name)=(TAGTEST) already exists. ) /var/www/discourse/vendor/bu Failed to handle exception in exception app middleware : PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_tags_on_name" DETAIL: Key (name)=(TAGTEST) already exists. Discourse 2.4.0.beta4

Any guidance would be appreciated!

[pfaffman (Jay Pfaffman)]

I had a similar issue. I describe how I fixed it in Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes), but it’s largely hand-waiving.