indexes-movement-to-tablespace (US018)

Automatic fix is not available.

What it does

Checks indexes movement to a different tablespace.

Why not?

Moving indexes to a different tablespace acquires an ACCESS EXCLUSIVE lock on the respective tables, blocking other accesses until the movement is completed. This will cause downtime if the tables are concurrently being accessed by other clients.

When should you?

If the tables are empty. If the tables are not empty but is not being concurrently accessed.

Use instead:

Have a look at pg_repack as an alternative.