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: [изображение] 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 r…

oh … the index is on LOWER(name) Run the query like so: select * from tags where name ilike 'chronicillness' You should be getting 2 rows.

select * from tags where name ilike 'chronicillness' id name topic_count created_at updated_at pm_topic_count target_tag 329 chronicillness 12 2017-08-22T00:17:38.824Z 2017-08-22T00:17:38.824Z 0 NULL 1710 chronicillness 2 2019-12-03T17:49:17.395Z 2019-12-03T17:49:17.395Z 0 NULL could i…

Well then that is the issue … I guess you delete 1710. 2 topics will be missing that tag afterwards.

#<Tag:0x00005607bb92cf48 id: 1710, name: "chronicillness", topic_count: 0, created_at: Tue, 03 Dec 2019 17:49:17 UTC +00:00, updated_at: Tue, 03 Dec 2019 17:49:17 UTC +00:00, pm_topic_count: 0, target_tag_id: nil> Why do I feel like it was a dwarf that wasn’t associated with anything?

Deleting the tag brought more stuff! discourse=# REINDEX SCHEMA CONCURRENTLY public; WARNING: cannot reindex invalid index "public.tags_pkey_ccnew" concurrently, skipping WARNING: cannot reindex invalid index "public.index_tags_on_name_ccnew" concurrently, skipping WARNING: cannot reindex invali…

Same fix :slight_smile: you got to repeat the process.

That’s what I was doing. but are those warnings okay? I don’t have to bother about those right?

yeah all warnings are correct, you have a corrupt index, it needs fixing first.

so all copycats are now gone and I’m only left with these warnings while reindexing: discourse=# REINDEX SCHEMA CONCURRENTLY public; WARNING: cannot reindex invalid index "public.tags_pkey_ccnew" concurrently, skipping WARNING: cannot reindex invalid index "public.index_tags_on_name_ccnew" concur…

[изображение] itsbhanusharma: tags_pkey_ccnew This is confusing to me… we have no index names than end with ccnew … did you create these by hand?

Corrupt indexes in PG12, how do I fix?

Поддержка Самостоятельное хостинг

sam (Sam Saffron) 25.Май.2020 03:16:47 11

Same fix you got to repeat the process.

1 лайк

Move a Discourse site to another VPS with rsync

Тема		Ответов	Просм.
Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes) Self-hosting	13	4723	05.02.2020
Restoring from backup failing: failure creating postgres index Self-hosting	7	980	28.05.2020
Restore fails - could not create unique index Self-hosting	22	3926	06.07.2020
2.7.0.beta2 upgrade failed with ERROR: duplicate key Self-hosting	25	2242	25.02.2021
PostgreSQL 13 update Announcements	3	11069	12.05.2025

Corrupt indexes in PG12, how do I fix?

Связанные темы