203
203
but not reads of the index's parent table. It also takes an exclusive lock
204
204
on the specific index being processed, which will block reads that attempt
205
205
to use that index. In contrast, <command>DROP INDEX</> momentarily takes
207
207
subsequent <command>CREATE INDEX</> locks out writes but not reads; since
208
208
the index is not there, no read will attempt to use it, meaning that there
209
209
will be no blocking but reads might be forced into expensive sequential