Hi, I’m trying to restore a backup on to a new Discourse instance as I am performing a server migration. Unfortunately I get this error: I’ve had a read of this: Restore fails - could not create unique index - #2 by simon and deleted the indexes. Now when I do: [2] pry(main)> IncomingReferer.wh…

Unfortunately this didn’t help, and I still get this message when restoring: [2021-07-03 16:53:41] ERROR: could not create unique index "index_incoming_referers_on_path_and_incoming_domain_id" [2021-07-03 16:53:41] DETAIL: Key (path, incoming_domain_id)=(/search, 4502) is duplicated. [2021-07-03 …

Something is still wrong. I am getting: [2021-07-03 17:28:53] ERROR: could not create unique index "index_incoming_referers_on_path_and_incoming_domain_id" [2021-07-03 17:28:53] DETAIL: Key (path, incoming_domain_id)=(/osmc/osmc, 2939) is duplicated. [2021-07-03 17:28:53] EXCEPTION: psql failed: …

[이미지] pfaffman: Can’t restore due to corrupt indexes (with some clues on how to deal with corrupt indexes) might offer some clues. Thanks. I’ve read this, but I don’t know what commands or queries to run to solve my problem. Sam

Basically, you want to try to rebuild the index and keep deleting stuff until you can reindex it. It looks like you’re doing the right stuff, you just need to keep doing it for all of the duplicate entries. If you have a budget you can post in Marketplace .

Hi Jay It’s not legal in the UK to expose our database to third parties to fix these issues, and even if it was, I have no interest in doing so for the interests of protecting user’s privacy. As an open source maintainer myself, the idea to take this to Marketplace is disappointing, particularly w…

Hey Sam. Sorry I wasn’t able to provide you with sufficient instruction to solve your problem yourself, but that’s how you made it sound. I thought it might be a relief rather than a disappointment that there are other ways to get your forum back online. Cheers

Hi Jay [이미지] pfaffman: Sorry I wasn’t able to provide you with sufficient instruction to solve your problem yourself, but that’s how you made it sound. I thought it might be a relief rather than a disappointment that there are other ways to get your forum back online. Not at all. You don’t o…

Unfortunately this is still a problem for us, and we cannot migrate servers, which is rather concerning. Happy to pay someone to get this solved, but after this issue, and the acknowledgement of it numerous times without a clear solution in the forum, we are seriously considering migrating to a dif…

There were indeed quite a few bugs in Postgres that would cause corrupted indexes. We think most of them are resolved in Postgres 13.x.

복원 실패: 고유 인덱스를 생성할 수 없음

제품 지원 자체 호스팅

pfaffman (Jay Pfaffman) 7월 3, 2021, 6:23오후 4

Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes) 에서는 몇 가지 힌트를 얻을 수 있습니다.

글		댓글	조회수
Backup restoration fails Self-hosting backups	16	556	6월 16, 2026
Restore fails - could not create unique index Self-hosting	21	4217	7월 4, 2020
Error on restore: could not create unique index Self-hosting	1	1898	3월 12, 2022
Restoring from backup failing: failure creating postgres index Self-hosting	7	1132	5월 28, 2020
Error importing backup: "could not create unique index" Self-hosting	6	1180	11월 1, 2021

복원 실패: 고유 인덱스를 생성할 수 없음

Related topics