2 ms·

I wouldn't recommend dropping large indexes within a transaction. Use DROP INDEX CONCURRENTLY instead, Without CONCURRENTLY it has to lock the table which can c

by jeltz 7y ago

I wouldn't recommend dropping large indexes within a transaction. Use DROP INDEX CONCURRENTLY instead, Without CONCURRENTLY it has to lock the table which can cause issues in high traffic databases. But this is mostly a moot point since 12 has REINDEX CONCURRENTLY.

paulddraper 7y ago
> it has to lock the table which can cause issues in high traffic databases In my case, I'm okay with a seconds-long lock while an index is dropped. An hours-long lock while an index is created is the real show stopper. > But this is mostly a moot point since 12 has REINDEX CONCURRENTLY. Fantastic.