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…

I think you can get the site back up with ./launcher start app Then take a look at ways to delete the duplicate: [image] Duplicate data explorer key blocking rebuild support Hey all, Rare I ask for help, but I’m puzzled about how to resolve this. Just rebuilt my site a…

[image] omarfilip: You do have two Did you visit my site? :wink: I see what you mean, when I search the in the GUI, I do see two. However, when I click on both as an admin and bring up the details page, they appear to be the same user. I can’t find a single detail that’s different between th…

[image] Gunnar: Did you visit my site? :wink: Of course! :grinning: That should delete 19732 but I can’t guarantee the absence of any ill effects. In any case, a backup before proceeding further is advisable.

You might also change the username of one of the duplicates.

[image] pfaffman: change the username Right. Once I do, should I be able to restart the upgrade from scratch? I.e. run rebuild twice? Thanks! Gunnar

That should work. Unless there are other duplicate users.

[image] pfaffman: Unless there are other duplicate users. Turns out there are, at least one. PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_users_on_username_lower" DETAIL: Key (username_lower)=(robs) already exists. Is there any way I can scan the datab…

[image] Gunnar: find them and fix them all before I try again A less invasive approach may be to reindex the database before upgrading and should tell you which ones need to be fixed. [image] Corrupt indexes in PG12, how do I fix? installation Sorry for bumping thi…

[image] omarfilip: reindex the database I’m not a database guy, so that looks scary. And if I read it correctly, you then end up with duplicate indices, and have to delete them manually? Besides, here’s the strange part. Like you found on my site with the previous duplicate, I found a duplic…

I tried rebuilding again, and found yet another duplicate with the username “drc”. In the GUI, I found these two: Deborah C David C Try clicking on either user to see their details on their profile “card”. You’ll see that no matter which of them you click, you’ll see the details for Deborah C. I…

I wonder what the following would return: select id, username FROM users WHERE username_lower = 'robs' OR username = 'RobS': It’s not something silly like one of the username entries has whitespace, or a non-printing character / unicode somehow in it?

La mise à niveau 2.7.0.beta2 a échoué avec l'erreur : clé dupliquée

Soutien Installation

omarfilip Janvier 23, 2021, 6:58 16

Une approche moins invasive consiste à réindexer la base de données avant la mise à niveau, ce qui devrait vous indiquer lesquels doivent être corrigés.

Sujet		Réponses	Vues
Upgrade failed with "duplicate key value violates unique constraint" error Self-hosting	18	2513	Mars 30, 2020
PG::UniqueViolation Problem during 3.1.0.beta4 upgrade Self-hosting	6	606	Mai 19, 2023
Upgrade Issues: Failed Upgrade due to Duplicate Key, Failed Snapshot Restore Self-hosting	7	1694	Avril 25, 2023
[Site Down :(] Upgrade\Rebuild Failure - DB Migration Issue? Self-hosting	9	681	Juin 19, 2023
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2011	Février 15, 2021

La mise à niveau 2.7.0.beta2 a échoué avec l'erreur : clé dupliquée

Sujets connexes