limiting postgresql

Andy Bradford amb-plug at
Mon Apr 21 20:55:41 MDT 2008

Thus said Kyle Waters on Mon, 21 Apr 2008 10:39:02 MDT:

> 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?

Is your  query doing some  kind of sequential  scan instead of  an index
scan? I suggest looking at the  actual query instead of trying to impose
limits. Maybe use a  bit of EXPLAIN ANALYZE to try  to figure out what's
going on.

[-----------[system uptime]--------------------------------------------]
  8:55pm  up 17 min,  1 user,  load average: 1.02, 1.22, 0.92

More information about the PLUG mailing list