non-concurrent-index-drop (US019)

Automatic fix is available.

What it does

Checks non-concurrent index drop.

Why not?

Dropping an index in non-concurrent mode acquires an ACCESS EXCLUSIVE lock on the table, blocking other accesses until the index drop is completed. This will cause downtime if the table is concurrently being accessed by other clients.

When should you?

If the table is empty. If the table is not empty but is not being concurrently accessed.

Use instead:

Drop the index in concurrent mode: DROP INDEX CONCURRENTLY ...