I was trying to restore my backup to a new server, and it showed some errors. The log is here: Ubuntu Pastebin The error maybe: PG::UniqueViolation: ERROR: could not create unique index "unique_index_categories_on_slug" DETAIL: Key (COALESCE(parent_category_id, '-1'::integer), slug)=(5, ) is du…

@Rasin , This should now be fixed as of: https://github.com/discourse/discourse/commit/7ba914f1e10d90b1e4d25b0ab2427c94df456eae Thank you for bringing this to our attention and I’m sorry for any inconvenience. Let us know if you have any other problems.

There is another thread with similar problem. It is a strange problem. Many of us have solved it just by keep trying. Try it several times and may one of them you don’t have the error. May be your problem is different but it resembles the database errors we had while restoring. It seems there i…

How strange is this solution…FML Will it be able to edit the sql file to make it normal? I mean, if I there any way to ignore the duplicated key?

And after I rebuild to a previous version or a beta version, the log has turned into: EXCEPTION: Compression::Strategy::ExtractFailed[2019-10-16 07:53:52] /var/www/discourse/lib/compression/strategy.rb:89:in `block in extract_file' /var/www/discourse/lib/compression/strategy.rb:85:in `open' /var/ww…

Take a look at: [이미지] Error Restoring Backup on Migration Bug @pfaffman Please increase the decompressed_file_max_size_mb site setting (it’s hidden). The default is currently set at 1GB. I have a PR ready to bump the default to 100GB but it wasn’t merged…

Thank you very much on this extracting thing! Could you please help me with the duplicated key error? Or is there a way I can fix this sql on psql?

[이미지] Rasin: The error maybe: PG::UniqueViolation: ERROR: could not create unique index "unique_index_categories_on_slug" DETAIL: Key (COALESCE(parent_category_id, '-1'::integer), slug)=(5, ) is duplicated. @daniel I think the migration in FIX: Add unique index to prevent duplicate slugs f…

Yes, I have told you: it is an odd thing. But it worked for several of us as you can read here: [이미지] Error Restoring Backup on Migration Bug Wow, trying to reproduce it so I can be sure that things will go as planned on migration, and I have the error ag…

Thank you for all your suggestions! Looking forward to new updates.

데이터베이스 복원 실패

지원 자체 호스팅

Rasin (Rasin) 10월 16, 2019, 7:12오전 3

이 해결책이 정말 이상하네요…FML
SQL 파일을 편집해서 정상적인 형태로 바꿀 수 있을까요?

즉, 중복된 키를 무시할 수 있는 방법이 있는지요?

글		댓글	조회수
Cannot restore database: sql key is duplicated Self-hosting	2	636	8월 30, 2022
Error restoring backup "key is duplicated" Self-hosting	7	1928	8월 30, 2017
SQL Error during import Self-hosting	18	2474	5월 3, 2015
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Self-hosting	7	1319	6월 20, 2022
Error on restore: could not create unique index Self-hosting	1	1869	3월 12, 2022

데이터베이스 복원 실패

Related topics