I attempted to move my Discourse to a new server and ran into an issue while restoring the backup: [2024-09-12 06:57:25] ERROR: could not create unique index "unique_post_links" [2024-09-12 06:57:25] DETAIL: Key (topic_id, post_id, url)=(2026, 4639, http://www.metronet.com/~mob) is duplicated. [2…

[image] omarfilip: There are many topics about fixing a corrupted index, but most are old It hasn’t happened in a while. It’s no different note than it was years ago. The thing to do is to rebuild that index on the other server (given that it’s still running) and delete (or otherwise repair)…

I got rid of the duplicates, but I’m left with these extra indexes that I think I should nuke. Can I drop all of these listed here? discourse=# REINDEX SCHEMA CONCURRENTLY public; WARNING: cannot reindex invalid index "public.topic_links_pkey_ccnew" concurrently, skipping WARNING: cannot reindex …

Fixing a corrupted index PG16.3 (unable to restore from backup - could not create unique index)

Product Support

itsbhanusharma (Bhanu Sharma) September 14, 2024, 6:29am 4

Anything with ccnew or ccnew’n’ should be safe to drop.

Topic		Replies	Views
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Self-hosting	7	1347	June 20, 2022
Error importing backup: "could not create unique index" Self-hosting	6	1185	November 1, 2021
Restore fails: could not create unique index Self-hosting	10	1361	February 13, 2022
Cannot restore database: sql key is duplicated Self-hosting	2	655	August 30, 2022
Error on restore: could not create unique index Self-hosting	1	1899	March 12, 2022

Fixing a corrupted index PG16.3 (unable to restore from backup - could not create unique index)

Related topics