Ich habe diese Schritte befolgt und den doppelten Benutzer erfolgreich umbenannt. Beim erneuten Indizieren bin ich jedoch auf dieses Problem gestoßen.
@sam hatte in diesem Thread vorgeschlagen: „Ja, bitte lösche die doppelten Zeilen (nuke the dupe rows)“, aber ich weiß nicht, was das im Kontext der Warnungen und Fehlermeldungen bedeutet, die ich beim erneuten Indizieren erhalte. Das Problem hat sich nun wie folgt entwickelt:
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.