I seem to have run into an issue when running the latest upgrade where it fails due to this: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_users_on_username_lower" DETAIL: Key (username_lower)=(scottie) already exists. I tried to recover by attempting to delet…

I had what u think was a similar case yesterday (see Help! Upgrade led to complete fail - #8 by Judith ). In broad strokes, I think you need to do something like rename the postgres_data _old back to postgres_data restart he old container fix the corrupt index problem by renaming the duplicate user…

@pfaffman - just pinged you via your contact form :slight_smile:

I replied. If you didn’t get it then maybe you put the wrong address?

To close the loop on this, @pfaffman is a wizard. He solved the problem with the forum upgrade (and a host of related issues) very quickly :slight_smile:

I am having the same issue, but not going to pay $500 for a solution. I have SFTP access to the server, so would it not be possible to just open the database in a notepad and rename the conflicted username? Or if anyone can fix it for like $50, please contact me.

You can check out PG::UniqueViolation Problem during 3.1.0.beta4 upgrade - #3 by ahmedeldeep where someone described pretty well what they did. You’ll need an SSH client, not SFTP. If you’re using Digital Ocean you can use the console on their web site.

Upgrade Issues: Failed Upgrade due to Duplicate Key, Failed Snapshot Restore

Поддержка Самостоятельное хостинг

GreXXL (Gregor Hammerschmidt) 10.Март.2021 09:15:28 2

You should look here - this seems to be the same issue: Help! Upgrade led to complete fail

Тема		Ответов	Просм.
Upgrade failed with "duplicate key value violates unique constraint" error Self-hosting	18	2472	30.03.2020
2.7.0.beta2 upgrade failed with ERROR: duplicate key Self-hosting	25	2245	25.02.2021
Urgent, upgraded build failed UniqueViolation Self-hosting	24	1632	20.02.2021
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	1962	15.02.2021
Error during upgrading from Beta 3.1.x to latest Self-hosting	3	827	20.01.2023

Upgrade Issues: Failed Upgrade due to Duplicate Key, Failed Snapshot Restore

Связанные темы