Hello Tibor, > You still have too many queries being executed.
Yes, and I have already popped all my relevant patches, and reapplied them (thanks, guilt!) them, and there is no CPU eating monster around. And now I'm starting to suspect something else that I have observed in this 1.1 bibsched that I didn't relate to my behaviour. I haven't finished my confirmation (I need some more time). The behaviour is that if, for whatever misterious reason, bibsched has old tasks that have not been executed when due (for example, yesterday or a couple of days ago), bibsched itself doesn't react, and I have to put in it manual mode, run each of them, and then put it in automatic mode. My hypothesis is that, _in this sleeping period_, bibsched loops infinitely. I've put bibsched in manual mode and I'll wait a couple of hours before puting it back in automatic mode. Meanwhile, I'm trying to follow the relevant SELECT statements, although the logic is quite hairy ;-) Ferran
