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

Großartig, danke für die Bestätigung!

Ich habe einen PR mit einer Korrektur dafür geöffnet:

github.com/discourse/discourse

FIX: Handle enum types during database restore

main ← 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	80	14. November 2024
Restore fails - could not create unique index Self-hosting	22	3918	6. Juli 2020
Upgrade failed with "duplicate key value violates unique constraint" error Self-hosting	18	2453	30. März 2020
Error restoring backup "key is duplicated" Self-hosting	8	1820	31. August 2017
Cannot restore database: sql key is duplicated Self-hosting	2	565	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