Discourse v2.8.13 (Ubuntu 20.04.6 LTS)에서 최신 버전으로 마이그레이션

[itsbhanusharma (Bhanu Sharma)]

@CamilleRoux

Failed to migrate default
#<StandardError:"An error has occurred, all later migrations canceled:\n\nPG::UniqueViolation: ERROR:  duplicate key value violates unique constraint \"index_users_on_username_lower\"\nDETAIL:  Key (username_lower)=(philippe) already exists.\n">

Key (username_lower)=(philippe) already exists.

어떤 조치를 시도하기 전에 전체 백업을 반드시 수행하십시오. 상황이 더 악화될 위험이 있습니다.

중복 오류를 처리하는 방법에 대한 지침을 제공하는 몇 가지 주제가 있습니다(진행을 계속하려면 기본적으로 중복 항목을 찾아 삭제해야 합니다)

2.7.0.beta2 업그레이드 실패: ERROR: duplicate key

I was upgrading from 2.7.0.beta1 and got this error message: 2021-01-22 20:16:22.015 UTC [4055] discourse@discourse LOG: duration: 75335.241 ms statement: UPDATE notifications SET processed = true 2021-01-22 20:16:23.792 UTC [4055] discourse@discourse LOG: duration: 1776.591 ms statement: ALTER TABLE "notifications" ALTER COLUMN "processed" SET NOT NULL 2021-01-22 20:16:25.198 UTC [4055] discourse@discourse LOG: duration: 1323.298 ms statement: CREATE INDEX "index_notifications_on_proce…

PG12에서 손상된 인덱스, 어떻게 수정하나요?

Sorry for bumping this once again, I got a very strange discourse=# REINDEX SCHEMA CONCURRENTLY public; ERROR: could not create unique index "index_tags_on_name_ccnew" DETAIL: Key (name)=(chronicillness) is duplicated. I’m assuming it can be fixed by the solution suggested above by @riking but I’m unable to figure out how to modify the syntax to suit my case.

업그레이드 중 오류: 중복 키 값이 고유 제약 조건을 위반합니다

Hello, I just used the upgrade tool to upgrade my discourse instance. Oddly, the forum is now down. When I tried to rebuild using the command line, I am getting this error: duplicate key value violates unique constraint "index_tags_on_lower_name" This error is repeated multiple times in the log so I recon its something about it. Here is the full logs: https://paste.apps.7ho.st/dezomakasu.sql (This is a portion of the logs, but here is the full log) Could anyone help me out? I also restored…