# הגירה נכשלה בשדרוג לגרסה האחרונה מלפני כשלושה שבועות

**URL:** <https://meta.discourse.org/t/migration-failed-upgrading-to-latest-from-3-weeks-ago/211450>\
**Category:** Self-hosting\
**Created:** [8 בדצמבר,‏ 2021,‏ 6:02am UTC](https://meta.discourse.org/t/migration-failed-upgrading-to-latest-from-3-weeks-ago/211450 "2021-12-08T06:02:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [8 בדצמבר,‏ 2021,‏ 6:22am UTC](https://meta.discourse.org/t/migration-failed-upgrading-to-latest-from-3-weeks-ago/211450/2 "2021-12-08T06:22:17Z")

</div>

Oh … we have seen this before on major version upgrades of PG. @saj recently worked on something here.

The long story is that on some PG upgrades the DB collation changes underneath you and you due to libc changing stuff. You have no choice but to reindex.

What happened to you is that:

1. You did a major upgrade
2. Your index become somewhat corrupt
3. A second insert of a user for `talk@remobjects.com` was made - you now have a duplicate row despite the index disallowing it.
4. We touch the row and it highlights this issue cause it can not update an unrelated column

Fix is:

- Find the user ids of the 2 users sharing the `talk@remobjects.com` email.
- Either delete or rename the email on one of them
- Proceed as planned
- Do a full db reindex urgently to catch other issues

---

_[View the full topic](https://meta.discourse.org/t/migration-failed-upgrading-to-latest-from-3-weeks-ago/211450)._
