Comment 3 for bug 911385

I think the behavior should be:

1. Get the resume db and tbl

2. If !$schema_iter->database_is_allowed || !$schema_iter->table_is_allowed then warn (unless --quiet) that resume would start on db.tbl but the db or table is filtered so resuming will begin instead with foo, where foo is the next permitted db tbl.

There might be a reason to skip the db or tbl that would be resumed. E.g. if db.foo is taking forever, the user ctrl-c's the tool, then does --ignore-table db.foo --resume because they know that table is too big and they just want to finish the rest of the tables, which case the warning might be nice to let the user know that tool is doing what they expect.