I’m getting this error when trying to update via ./launcher rebuild app ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: could not create unique index "index_discourse_solved_solved_topics_on_answer_post_id" (ActiveRecord::RecordNotUnique) DETAIL: Key (answer_post_id)=(201795) is dupli…

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 (UTC) [image] nattsw …

ERROR RecordNotUnique on index_discourse_solved_solved_topics_on_answer_post_id

Support

fhe (Florian) March 26, 2025, 5:07pm 9

Excellent! Thanks for the heads up — I’ve marked your post as solution.

2 Likes

Topic		Replies	Views
Error importing backup: "could not create unique index" Installation	7	964	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	1117	June 20, 2022
PG::UniqueViolation Problem during 3.1.0.beta4 upgrade Installation	6	535	May 19, 2023
Restore fails - could not create unique index Installation	22	3724	July 6, 2020

ERROR RecordNotUnique on index_discourse_solved_solved_topics_on_answer_post_id

Related topics