ERROR RecordNotUnique en index_discourse_solved_solved_topics_on_answer_post_id

thoka · 26 Marzo, 2025 17:04

Parece que se ha solucionado con este parche:

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.

Tema		Respuestas	Vistas
"discourse_solved_solved_topics" violates not-null constraint during rebuild Product Support solved	9	355	21 Diciembre 2025
Cannot restore database: sql key is duplicated Self-hosting	2	655	30 Agosto 2022
Restore fails - could not create unique index Self-hosting	21	4216	4 Julio 2020
Update failed - PG::UniqueViolation: ERROR Self-hosting	7	955	21 Diciembre 2018
Error restoring backup "key is duplicated" Self-hosting	7	1989	30 Agosto 2017

ERROR RecordNotUnique en index_discourse_solved_solved_topics_on_answer_post_id

Temas relacionados