# 更新到 2.4.0beta10 后，某些类别中的部分主题无法查看

**URL:** <https://meta.discourse.org/t/after-updating-to-2-4-0beta10-some-topics-from-a-specific-category-are-not-viewable/141115>\
**Category:** Support\
**Created:** [2020年二月9日 16:46 UTC](https://meta.discourse.org/t/after-updating-to-2-4-0beta10-some-topics-from-a-specific-category-are-not-viewable/141115 "2020-02-09T16:46:43Z")\
**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:** [2020年二月10日 00:20 UTC](https://meta.discourse.org/t/after-updating-to-2-4-0beta10-some-topics-from-a-specific-category-are-not-viewable/141115/2 "2020-02-10T00:20:09Z")

</div>

这看起来像是索引损坏，我猜该表中可能存在重复数据。

建议先删除重复的行，不过我不确定是如何导致这种情况的。

我们之前遇到过类似的索引损坏问题：

> [@Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes)](https://meta.discourse.org/t/cant-restore-due-to-corrupt-indexes-with-some-clues-on-how-to-deal-with-corrupt-indexes/137400):
>
> This backup failed several times because of errors like ERROR: could not create unique index "index\_incoming\_referers\_on\_path\_and\_incoming\_domain\_id" DETAIL: Key (path, incoming\_domain\_id)=(/@dataandme, 41) is duplicated. ERROR: current transaction is aborted, commands ignored until end of transaction block I went and removed all of those records by hand in rails with stuff like IncomingReferer.where(path: ‘/@dataandme’).destroy\_all Now it’s still failing and I ... [2019-1…

---

_[View the full topic](https://meta.discourse.org/t/after-updating-to-2-4-0beta10-some-topics-from-a-specific-category-are-not-viewable/141115)._