non-concurrent-index-creation (US016)

Automatic fix is available.

What it does

Checks non-concurrent index creation.

Why not?

Creating an index in non-concurrent mode will locks out writes (but not reads) on the table until it is done. This will cause downtime if the table is concurrently being written by other clients.

When should you?

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

Use instead:

Create the index in concurrent mode: CREATE .. INDEX CONCURRENTLY ON ...