Some people asked whether they should be running the maintenance script after seeing a PgHero warning about duplicate indexes.
This change highlights that the warning is unrelated to database index corruption.
- emphasizes that Mastodon has to be stopped when running the script
- add `RAILS_ENV=production` in front of the `tootctl` line as it is a common mistake to run it without `RAILS_ENV` set
- mention 3.2.2 as the first release shipping the script (assuming that will be the case)
* [WiP] Add documentation about index corruption
Add documentation about index corruption caused by changes in collation rules, and information on how to fix it.
* Add doc on how to check indexes
Add documentation on how to check indexes without bringing the instance down.
* Update index-corruption.md
* fixup typo
* Add instructions for re-creating the database
* Add minor explanations
* Remove recommendation to re-create database with C collation
Meaningful case-folding operations are used within the database for hashtags, so do not recommend using `C`, which would cause issues with non-ASCII hashtags.
Claire