limiting postgresql

Kyle Waters unum at
Mon Apr 21 10:39:02 MDT 2008

    I have a a web application where a certain process ties up 100% of 
my cpu.  If two people are looking at that process both of my cpu's are 
tied up at 100%.  This slows down other people trying to use the 
database for more trivial tasks.  I'd like to prioritize the smaller 
tasks if possible, or at least make it so postgres can't take up 100% of 
the processor with one task.  Any suggestions?


More information about the PLUG mailing list