J’ai suivi ces étapes et renommé avec succès l’utilisateur en double. Cependant, j’ai ensuite rencontré ce problème en tentant de réindexer.
@sam avait suggéré dans ce fil : « Oui, supprimez les lignes en double », mais je ne sais pas ce que cela signifie dans le contexte des avertissements et des messages d’erreur que je reçois lors de la réindexation, qui a maintenant pris de l’ampleur :
REINDEX SCHEMA CONCURRENTLY public;
WARNING: cannot reindex invalid index "public.index_incoming_referers_on_path_and_incoming_domain_id_ccnew" concurrently, skipping
WARNING: cannot reindex invalid index "public.incoming_referers_pkey_ccnew1" concurrently, skipping
WARNING: cannot reindex invalid index "public.index_incoming_referers_on_path_and_incoming_domain_id_ccnew1" concurrently, skipping
WARNING: cannot reindex invalid index "public.index_incoming_referers_on_path_and_incoming_domain_id_cc_ccnew" concurrently, skipping
WARNING: cannot reindex invalid index "public.index_incoming_referers_on_path_and_incoming_domain_id_c_ccnew1" concurrently, skipping
WARNING: cannot reindex invalid index "public.incoming_referers_pkey_ccnew2" concurrently, skipping
WARNING: cannot reindex invalid index "public.index_incoming_referers_on_path_and_incoming_domain_id_ccnew2" concurrently, skipping
WARNING: cannot reindex invalid index "public.incoming_referers_pkey_ccnew_ccnew" concurrently, skipping
WARNING: cannot reindex invalid index "pg_toast.pg_toast_19250_index_ccnew1" concurrently, skipping
WARNING: cannot reindex invalid index "pg_toast.pg_toast_19250_index_ccnew2" concurrently, skipping
WARNING: cannot reindex invalid index "pg_toast.pg_toast_19250_index_ccnew_ccnew" concurrently, skipping
ERROR: could not create unique index "index_incoming_referers_on_path_and_incoming_domain_id_ccnew3"
DETAIL: Key (path, incoming_domain_id)=(/votes/, 1165) is duplicated.