justin <jtyme@intrusic.com> writes:
> I'm currently in the midst of working on a serializable transaction
> which drops indexes on several tables, does a bulk copy, and rebuilds
> the indexes. Based on what I've read it seemed as though I'd be able to
> concurrently execute read only queries against these tables,
Nope, because "drop index" obtains an exclusive lock on the table.
(If it didn't, some other query might try to *use* the index, which
would create a bit of a problem if the DROP committed midway through.)
regards, tom lane