A failed CREATE INDEX CONCURRENTLY leaves an INVALID index behind. Reproduce it, find it in pg_index, drop it safely, and stop the transaction-block error.
Plain CREATE INDEX takes a SHARE lock and blocks INSERT/UPDATE/DELETE until the build finishes. CREATE INDEX CONCURRENTLY avoids that, but Postgres refuses it inside a transaction block, and most migration tools wrap every migration in one.
Just curious as to what peoples thoughts are on reading more than 1 book at a time and reading whichever you feel like most each day. If yes, why do you read more than one at a time, and how do you decide what books can be read at the same time as each…