Segui esses passos e renomeei com sucesso o usuário duplicado. Mas, ao tentar reindexar, encontrei este problema.
@sam havia sugerido naquele tópico: “Sim, por favor, elimine as linhas duplicadas”, mas não sei o que isso significa no contexto dos avisos e mensagens de erro que recebo ao reindexar, o que agora se agravou para:
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.