From d5d88f2c3722e6774be9f7a4016179d91f24e6c3 Mon Sep 17 00:00:00 2001 From: Claire Date: Sun, 16 Jan 2022 16:37:06 +0100 Subject: [PATCH] Add an info box about PgHero duplicate index warnings (#909) 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. --- content/en/admin/troubleshooting/index-corruption.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/en/admin/troubleshooting/index-corruption.md b/content/en/admin/troubleshooting/index-corruption.md index 80f16317..6ca6f1c4 100644 --- a/content/en/admin/troubleshooting/index-corruption.md +++ b/content/en/admin/troubleshooting/index-corruption.md @@ -24,6 +24,10 @@ More information: https://wiki.postgresql.org/wiki/Locale_data_changes https://p If your database is not using `C` or `POSIX` for its collation setting (which you can check with `SELECT datcollate FROM pg_database WHERE datname = current_database();`), your indexes might be inconsistent, if you ever ran with a version of glibc prior to 2.28 and did not immediately reindex your databases after updating to glibc 2.28 or newer. +{{< hint style="info" >}} +You may have found this page because of **PgHero** warnings about "Duplicate Indexes". While such warnings can sometimes be indicative of an issue in deploying or updating Mastodon, **they are not related to database index corruption and not indicative of any functional issue with your database**. +{{< /hint >}} + You can check whether your indexes are consistent using [PostgreSQL's `amcheck` module](https://www.postgresql.org/docs/10/amcheck.html): as the database server's super user, connect to your Mastodon database and issue the following (this may take a while): ```SQL