Fout RecordNotUnique op index_discourse_solved_solved_topics_on_answer_post_id

thoka · 26 maart 2025 om 17:04

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		Antwoorden	Weergaven
"discourse_solved_solved_topics" violates not-null constraint during rebuild Support solved	9	135	21 december 2025
Cannot restore database: sql key is duplicated Self-hosting	2	568	30 augustus 2022
Restore fails - could not create unique index Self-hosting	22	3922	6 juli 2020
Update failed - PG::UniqueViolation: ERROR Self-hosting	8	829	14 november 2021
Error restoring backup "key is duplicated" Self-hosting	8	1821	31 augustus 2017

Fout RecordNotUnique op index_discourse_solved_solved_topics_on_answer_post_id

Gerelateerde topics