Looks like 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: