"Bergquist, Brett" <[email protected]> writes: > If I have a table with millions of rows and I invoke > syscs_util.update_statistics on it, will the table/indexes be lock > such that inserts or updates will fail while this is being done.
It used to lock the table exclusively, but that was fixed in DERBY-4274/Derby 10.5.2.0. Now it should only take an intention lock on the table, which prevents other transactions from dropping the table, but inserts and updates won't be blocked. -- Knut Anders
