Upgrade schlägt fehl bei dupliziertem Schlüssel-Fehler ("Index, um hotlinked Media auf post id und url md5 zu indexieren")

david · 3. Mai 2022 um 21:30

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)

Thema		Antworten	Aufrufe
Restore fails with "hotlinked_media_status" already exists Support	7	66	14. November 2024
Restore fails - could not create unique index Installation	22	3786	6. Juli 2020
Upgrade failed with "duplicate key value violates unique constraint" error Installation	18	2401	30. März 2020
Error restoring backup "key is duplicated" Installation	8	1802	31. August 2017
Cannot restore database: sql key is duplicated Installation	2	549	30. August 2022

Upgrade schlägt fehl bei dupliziertem Schlüssel-Fehler ("Index, um hotlinked Media auf post id und url md5 zu indexieren")

Verwandte Themen