Invalid Indexes

Check Frequency

Every 30 minutes

Default Configuration

Detects indexes that are not recognized as valid in Postgres and creates an issue with severity "info". These indexes typically are left over when using CREATE INDEX CONCURRENTLY and the command fails or is aborted by the user. Resolves once the index has been dropped.

This check is enabled by default.



Invalid indexes take up disk space but are not usable by queries.


You can clean up this ununsed index by running DROP INDEX CONCURRENTLY "<index_name>";.

Couldn't find what you were looking for or want to talk about something specific?
Start a conversation with us →