:joy::joy: I… version is v1.9.0.beta7 +341 [2017-08-29 15:27:03] ERROR: could not create unique index "index_topic_users_on_topic_id_and_user_id" [2017-08-29 15:27:03] DETAIL: Key (topic_id, user_id)=(59700, 11226) is duplicated. [2017-08-29 15:27:03] ERROR: current transaction is aborted, commands ignored until end of transaction block [2017-08-29 15:27:03] ERROR: current transaction is aborted, commands ignored until end of transaction block [2017-08-29 15:27:03] ERROR: current transaction is aborted, commands ignored until end of transaction block [2017-08-29 15:27:03] ERROR: current transaction is aborted, commands ignored until end of transaction block .... [2017-08-29 15:27:03] EXCEPTION: psql failed [2017-08-29 15:27:03] /var/www/discourse/lib/backup_restore/restorer.rb:279:in `restore_dump' /var/www/discourse/lib/backup_restore/restorer.rb:42:in `run' /var/www/discourse/lib/backup_restore/backup_restore.rb:163:in `block in start!' /var/www/discourse/lib/backup_restore/backup_restore.rb:160:in `fork' ...

now, I just have backup tar.gz, my old server has been resintall OS/ Plz help me .:disappointed_relieved:

I’ve seen a few similar reports like https://meta.discourse.org/t/error-could-not-create-unique-index-badges-pkey-attempting-to-restore-backup/67726. I suspect that there is a bug somewhere, but no one has shown a way to replicate it. I think your solution is to do this: Manually create and restore Discourse backups.

:disappointed_relieved::disappointed_relieved: but the server has reinstll OS, so I lost my forum 50,000 user. :persevere::persevere:

That looks a lot like this one: [image] Update failed due to primary key sequence error Self-hosting I’ve tried to update from Version v1.9.0.beta4 +300 to 1.9.0.beta5 by pulling the latest changes (git pull) and try to rebuild the app (./launcher rebuild app), but the migration failed with the following message: Any fix? I, [2017-08-11T05:43:33.644343 #15] INFO -- : > cd /var/www/discourse && su dis course -c 'bundle exec rake db:migrate' 2017-08-11 05:43:38.795 UTC [399] discourse@discourse ERROR: duplicate key valu …

discourse=> select * from topic_users where id=59700; user_id | topic_id | posted | last_read_post_number | highest_seen_post_number | last_visited_at | first_visited_at | notification_level | notifications_changed_at | notifications_reason_id | total_msecs_viewed | cleared_pinned_at | id | last_emailed_post_number | liked | bookmarked ---------+----------+--------+-----------------------+--------------------------+----------------------------+----------------------------+--------------------+----------------------------+-------------------------+--------------------+-------------------+-------+--------------------------+-------+------------ 1 | 11091 | t | 1 | 1 | 2017-02-13 12:51:41.857104 | 2017-02-13 12:51:41.857104 | 3 | 2017-02-13 12:51:41.855492 | 1 | 0 | | 59700 | | f | f (1 row) ~

I have fix this. vi .sql file, delete all include 59700 and 11226 :joy::joy::joy: everything is fine.

Error restoring backup "key is duplicated"

Product Support Self-hosting

codinghorror (Jeff Atwood) August 30, 2017, 12:16am 5

That looks a lot like this one:

Topic		Replies	Views
Cannot restore database: sql key is duplicated Self-hosting	2	666	August 30, 2022
Backup restoration fails Self-hosting backups	16	589	June 16, 2026
Restore fails - could not create unique index Self-hosting	21	4244	July 4, 2020
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Self-hosting	7	1370	June 20, 2022
Error on restore: could not create unique index Self-hosting	1	1916	March 12, 2022

Error restoring backup "key is duplicated"

Related topics