好的,我已经修复了。我执行了以下操作:
进入容器
./launcher enter app
连接到数据库
su postgres -c 'psql discourse'
尝试查找重复项
discourse=# select * from incoming_referers where path LIKE '%/search/' ORDER BY incoming_domain_id;
id | path | incoming_domain_id
------+------------+--------------------
3339 | /search/ | 33
6257 | /search/ | 91
1567 | /search/ | 298
1777 | /search/ | 341
3010 | /search/ | 418
6247 | /search/ | 418
4293 | /search/ | 644
2899 | /search/ | 653
3447 | /search/ | 793
3696 | /search/ | 852
4395 | /a/search/ | 1050
6968 | /search/ | 1305
5634 | /search/ | 1387
5834 | /search/ | 1437
6519 | /search/ | 1637
7127 | /search/ | 1787
7280 | /search/ | 1827
(17 rows)
删除重复项
DELETE FROM incoming_referers WHERE path LIKE '%/search/' AND id IN (6247);
然后重建
discourse=# REINDEX SCHEMA CONCURRENTLY public;
WARNING: cannot reindex invalid index "public.incoming_referers_pkey_ccnew" concurrently, skipping
WARNING: cannot reindex invalid index "public.index_incoming_referers_on_path_and_incoming_domain_id_ccnew" concurrently, skipping
WARNING: cannot reindex invalid index "pg_toast.pg_toast_20732_index_ccnew" concurrently, skipping
REINDEX
之后我再次进行了备份,将其复制到新服务器,并成功导入 ![]()
如果备份过程能够检测重复项以避免任何问题就好了。我很幸运还能访问仍在运行的原始服务器。如果我在恢复冷备份,这可能会成为一个更大的问题。
非常感谢您的帮助。