Brion VIBBER wrote:
The error message comes up on the mysql_select_db, and is the first thing we do after opening a connection; but since we're using persistent connections, it could be left in an odd state after the last process...?
I've tweaked it so if it can't select the database, it will try again with a spankin' new connection (via mysql_connect()) and make a note in the logfile. So, with any luck, this should at least work around the problem.
Restarting apache should clear the mysterious borken connections, since the persistent connections are associated with individual child processes. (At least, that's what the documentation leads me to believe...)
-- brion vibber (brion @ pobox.com