Hello,
It seems it was indeed postgres that was causing the troubles, or to
be more precise, the fact that I had forgotten to set the
auto-vacuumer. I've manually vacuumed everything (it took hours) and
things seem to be alright once more in the Lancaster d-cache world. I
also took the opportunity to switch on the auto-vacuuming so hopefully
something like this won't happen again.
Thanks for all the help and sagely advice chaps,
Matt
|