Ripristino dal backup fallito: errore nella creazione dell'indice postgres

[Dustin_Lang]

Wow, sarebbe davvero bello se il processo di aggiornamento potesse risolvere alcuni di questi problemi!

Quindi, dopo aver installato il plugin Data Explorer e dato un’occhiata all’indice incoming_referers, oltre a eliminare altri indici elencati nella query qui:

Corrupt indexes in PG12, how do I fix?

If a concurrent REINDEX fails because the table has invalid data, you need to: Fix the invalid data, like it was done here. List the invalid indexes using SELECT pg_class.relname FROM pg_class, pg_index WHERE pg_index.indisvalid = false AND pg_index.indexrelid = pg_class.oid; Drop each invalid index listed above using DROP INDEX <indexname>; Try the REINDEX again.

Sto ancora ottenendo:

discourse=# REINDEX SCHEMA CONCURRENTLY public;
WARNING:  cannot reindex invalid index "pg_toast.pg_toast_19337_index_ccnew" concurrently, skipping
WARNING:  cannot reindex invalid index "pg_toast.pg_toast_19337_index_ccnew1" concurrently, skipping

E quelli non vogliono essere eliminati!

# drop index pg_toast_19337_index_ccnew1;
ERROR:  index "pg_toast_19337_index_ccnew1" does not exist