Migración de discourse v2.8.13 (en Ubuntu 20.04.6 LTS) a la última versión

[itsbhanusharma (Bhanu Sharma)]

@CamilleRoux

Failed to migrate default
#<StandardError: "An error has occurred, all later migrations canceled:

PG::UniqueViolation: ERROR:  duplicate key value violates unique constraint "index_users_on_username_lower"
DETAIL:  Key (username_lower)=(philippe) already exists.
">

Key (username_lower)=(philippe) already exists.

Realice una copia de seguridad completa antes de intentar solucionar cualquier problema, ya que existe el riesgo de que lo empeore aún más.

Hay algunos temas que proporcionan orientación sobre cómo lidiar con errores de duplicación (básicamente, tiene que encontrar y eliminar los duplicados antes de continuar)

2.7.0.beta2 upgrade failed with 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…

Corrupt indexes in PG12, how do I fix?

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.

Problem in upgrade: duplicate key value violates unique constraint

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…