# Restore fails - could not create unique index

**URL:** <https://meta.discourse.org/t/restore-fails-could-not-create-unique-index/151380>\
**Category:** Self-hosting\
**Created:** [13 mei 2020 om 20:29 UTC](https://meta.discourse.org/t/restore-fails-could-not-create-unique-index/151380 "2020-05-13T20:29:04Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [18 mei 2020 om 22:20 UTC](https://meta.discourse.org/t/restore-fails-could-not-create-unique-index/151380/21 "2020-05-18T22:20:34Z")

</div>

> [@sam](#):
>
> My guess is that is something todo with some sort of rude shutdown of the db engine, maybe on power loss

That’s a reasonable explanation. Does `./launcher shutdown app` (or rebuild) do a clean shutdown or postgres somehow? Oh, but I bet that an unattended upgrade doesn’t know how to do a clean shutdown of docker containers, does it?

---

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