Upgrade fails on duplicate key error ("index post hotlinked media on post id and url md5")

david · May 3, 2022, 9:30pm

Great, thanks for confirming!

I opened a PR with a fix for that one:

github.com/discourse/discourse

FIX: Handle enum types during database restore

discourse:main ← discourse:fix-restore-enums

opened 09:27PM - 03 May 22 UTC

davidtaylorhq

+9 -0

c1db9687 introduced an postgres enum type. Our database restore logic did not ha…ndle custom types correctly, and would therefore raise a 'type already exists' error when restoring any backup. This commit adds restore handling for enums, mirroring the similar logic for tables and views. --- (This code is not tested by rspec, but it is tested by a regular internal job at CDCK, which correctly picked up on this issue)

Topic		Replies	Views
Restore fails with "hotlinked_media_status" already exists Support	7	64	November 14, 2024
Restore fails - could not create unique index Installation	22	3773	July 6, 2020
Upgrade failed with "duplicate key value violates unique constraint" error Installation	18	2386	March 30, 2020
Error restoring backup "key is duplicated" Installation	8	1784	August 31, 2017
Cannot restore database: sql key is duplicated Installation	2	543	August 30, 2022

Upgrade fails on duplicate key error ("index post hotlinked media on post id and url md5")

Related topics