ERROR RecordNotUnique on index_discourse_solved_solved_topics_on_answer_post_id

thoka · March 26, 2025, 5:04pm

Seems to be fixed with this patch:

FIX: Multiple topics may have the same post as its solution (#348)

committed 02:21PM - 26 Mar 25 UTC

We are seeing some errors when migrating and adding indexes on `answer_post_id`.… ``` #<StandardError:"An error has occurred, all later migrations canceled:\n\nPG::UniqueViolation: ERROR: could not create unique index \"index_discourse_solved_solved_topics_on_answer_post_id\"\nDETAIL: Key (answer_post_id)=(13006) is duplicated.\n"> ``` This PR modifies the earlier migration, and also adds one before the addition of indexes to remove duplicates.

Topic		Replies	Views
Error importing backup: "could not create unique index" Installation	7	961	November 1, 2021
Fixing a corrupted index PG16.3 (unable to restore from backup - could not create unique index) Support	3	59	September 14, 2024
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Installation	8	1115	June 20, 2022
PG::UniqueViolation Problem during 3.1.0.beta4 upgrade Installation	6	534	May 19, 2023
Restore fails - could not create unique index Installation	22	3722	July 6, 2020

ERROR RecordNotUnique on index_discourse_solved_solved_topics_on_answer_post_id

Related topics