This looks to have been a temporary issue with the database server - I haven't had a flood of error emails about it, so it's hard to say what might have caused it otherwise.