# בנייה מחדש של אינדקסים לא תקינים

**URL:** <https://meta.discourse.org/t/rebuilding-invalid-indexes/177599>\
**Category:** Self-hosting\
**Created:** [28 בינואר,‏ 2021,‏ 8:45pm UTC](https://meta.discourse.org/t/rebuilding-invalid-indexes/177599 "2021-01-28T20:45:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [28 בינואר,‏ 2021,‏ 8:49pm UTC](https://meta.discourse.org/t/rebuilding-invalid-indexes/177599/2 "2021-01-28T20:49:27Z")

</div>

[Looks like](https://paquier.xyz/postgresql-2/postgres-12-reindex-concurrently/) the `_ccnew` index is part of how the concurrent reindex happens:

> - Create a new index in the catalogs which is a copycat of the one reindexed (with some exceptions, for example partition indexes don’t have their inheritance dependency registered at creation, but at swap time). This new, temporary is suffixed with “\_ccnew”. Bref.

Can you reindex those indexes without the `concurrently` keyword?

or, from later in that post:

> Then, REINDEX TABLE CONCURRENTLY will _skip_ invalid indexes because in the event of successive and multiple failures then the number of indexes would just ramp up, doubling at each run, causing a lot of bloat on the follow-up reindex operations:  
> …  
> It is however possible to reindex invalid indexes with just REINDEX INDEX CONCURRENTLY:

---

_[View the full topic](https://meta.discourse.org/t/rebuilding-invalid-indexes/177599)._
