Comment 5 for bug 680802

In this particular case I wouldn't invest into fancy reporting just yet. The Recife change may have eliminated any remaining instances of the timeout.

I'd just log a message, let the thing run for a while, and then see what follow-up is appropriate. Chances are that either we can remove the query timeout now, or we'll find it easier to diagnose the problem.