From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | matt(at)followers(dot)net |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Preventing query from hogging server |
Date: | 2005-03-24 20:19:02 |
Message-ID: | 5369.1111695542@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Matthew Nuzum" <matt(dot)followers(at)gmail(dot)com> writes:
> Thanks. Other than avoiding using too much sort mem, is there anything else
> I can do to ensure this query doesn't starve other processes for resources?
Not a lot.
> Doing the explain analyze only increases my server load by 1 and seems to
> readily relinquish CPU time, but previously when I had been running a test
> query my server load rose to unacceptable levels.
Interesting. EXPLAIN ANALYZE is going to cause a bunch of
gettimeofday() calls to be inserted ... maybe your kernel takes those as
process preemption points? Seems unlikely, but ...
> FWIW, the explain was run from psql running on the db server, the test query
> the other day was run from one of the webservers. Should I run this on the
> db server to minimize load?
Since it's an insert/select, psql isn't participating in the data flow.
It's not going to matter where the psql process is.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2005-03-24 20:25:48 | Re: pg_autovacuum not having enough suction ? |
Previous Message | Matthew Nuzum | 2005-03-24 20:13:01 | Re: Preventing query from hogging server |