Hmm, are there triggers on wss_entries that are UPDATEing/DELETEing entries elsewhere?
No, that table is pretty much stand-alone. What we're seeing here is most likely caused by the initial copy of the legacy db tables.
This happens when creating the local test db which I do right before the tests. I can avoid the issue if I monitor top and wait for the analyze to complete on all the related tables.
