On Fri, Jul 18, 2008 at 10:05:33AM +0530, Gurjeet Singh wrote:
> I just ran DROP SCHEMA _<slony schema> CASCADE; and it spiked again, on a > very low loaded box!!
Ah, well, if slony is involved, then you have possible locking problems in the database _also_ to contend with, along with the spinlock problems. This will for sure cause spikes.
You need to tell us more about what you're doing. And I bet some of it belongs on the slony lists.
I am in the eye of the storm right now.
Just started INIT cluster Slonik command and that spiked too.. for more than 10 minutes now!!
