# דחוף, בנייה משודרגת נכשלה UniqueViolation

**URL:** <https://meta.discourse.org/t/urgent-upgraded-build-failed-uniqueviolation/176858>\
**Category:** Self-hosting\
**Created:** [21 בינואר,‏ 2021,‏ 6:55pm UTC](https://meta.discourse.org/t/urgent-upgraded-build-failed-uniqueviolation/176858 "2021-01-21T18:55:14Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [21 בינואר,‏ 2021,‏ 8:41pm UTC](https://meta.discourse.org/t/urgent-upgraded-build-failed-uniqueviolation/176858/22 "2021-01-21T20:41:46Z")

</div>

Thinking about this, outside your container try to rename your old postgres file and renaming the new one \_new

Then try to restart the service within docker

files are in `/var/discourse/shared/standalone` outside the container.

1. rename `postgres_data` to `postgres_data_new`
2. rename `postgres_data_old` to `postgres_data`
3. restart service inside container as above
4. check it’s started again with logs inspection.
5. If good, you can proceed with fixing the data.

---

_[View the full topic](https://meta.discourse.org/t/urgent-upgraded-build-failed-uniqueviolation/176858)._
