# Restore fails: could not create unique index

**URL:** <https://meta.discourse.org/t/restore-fails-could-not-create-unique-index/195867>\
**Category:** Self-hosting\
**Created:** [July 3, 2021, 4:23pm UTC](https://meta.discourse.org/t/restore-fails-could-not-create-unique-index/195867 "2021-07-03T16:23:18Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![samnazarko](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/samnazarko/32/109010_2.png) [@samnazarko](https://meta.discourse.org/u/samnazarko)\
**Post date:** [July 3, 2021, 11:20pm UTC](https://meta.discourse.org/t/restore-fails-could-not-create-unique-index/195867/7 "2021-07-03T23:20:43Z")

</div>

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 when there seems to be a tacit acknowledgement that the issues are introduced by a Postgres update which Discourse bundled in their Docker container. We use Discourse in the Docker container because we understand the closely coupled dependencies and want to devolve the version and dependency management to the Discourse team’s expertise.

It seems to be accepted that this is a Postgres 12 regression and there are some potential mitigations. However, first reports came in over a year ago and I am sure there will be more affected users in the future if they try and restore a backup.

I would prefer to sponsor some development time to fix this in Discourse upstream so others can also benefit from this. In the interim, our forum is not functional and I will need to consult help with someone with Postgres DBA knowledge.

Cheers

Sam

---

_[View the full topic](https://meta.discourse.org/t/restore-fails-could-not-create-unique-index/195867)._
