Kurt, > This is without any other query running, right? I even find 5000 > cs/s rather large if there isn't any other process that wants > some CPU.
Sorry! Darn! Important fact left out of the problem description: The issue happens when *two or more* intensive queries are running simultaneosly. > To me this can only make sense in case there is an other backend > trying to use the same memory, and it needs to be moved from 1 > CPU to an other. Yes. See above. -- Josh Berkus Aglio Database Solutions San Francisco ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
