Sorry for bumping this once again, I got a very strange discourse=# REINDEX SCHEMA CONCURRENTLY public; ERROR: could not create unique index "index_tags_on_name_ccnew" DETAIL: Key (name)=(chronicillness) is duplicated. I’m assuming it can be fixed by the solution suggested above by @riking but I…

See: [Bild] Peter Geoghegan (petervgeoghegan) @codinghorror @shog9 I work on the Postgres B-Tree code. Corruption simply should not happen with any regularity. E-mail me (address is pg@bowt.ie ), or send a report to one of the community lists. Always interested in hearing problem reports,…

Corrupt indexes in PG12, how do I fix?

Unterstützung Installation

sam (Sam Saffron) 25. Mai 2020 um 03:16 11

Same fix you got to repeat the process.

1 „Gefällt mir“

Move a Discourse site to another VPS with rsync

Thema		Antworten	Aufrufe
Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes) Self-hosting	13	4719	5. Februar 2020
Restoring from backup failing: failure creating postgres index Self-hosting	7	978	28. Mai 2020
Restore fails - could not create unique index Self-hosting	22	3922	6. Juli 2020
2.7.0.beta2 upgrade failed with ERROR: duplicate key Self-hosting	25	2232	25. Februar 2021
PostgreSQL 13 update Announcements	3	11061	12. Mai 2025

Corrupt indexes in PG12, how do I fix?

Verwandte Themen