Comment 7 for bug 408718

Ok, so we've seen this again with exactly the same query. This is what I want to do to fix this:

 1. introduce a timeout on this query of about 5 minutes
 2. after that, abort the transaction, restart it, and go on with life without super-fast-imports

To be able to test this in any meaningful way possible, I'll probably make timeout value a config option.