| From: | Claus Guttesen <kometen(at)gmail(dot)com> |
|---|---|
| To: | jesper(at)krogh(dot)cc |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Speed while runnning large transactions. |
| Date: | 2009-09-24 08:41:44 |
| Message-ID: | b41c75520909240141k4dba6089n7907930cfa535890@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> I have a transaction running at the database for around 20 hours .. still
> isn't done. But during the last hours it has come to the point where it
> really hurts performance of "other queries".
>
> Given pg_stat_activity output there seems to be no locks interfering but
> the overall cpu-usage of all queries continue to rise. iowait numbers are
> also very low.
>
> What can I do to make the system handle other queries better?
Can you post the query? Do you 'vacuum analyze' on a regular basis?
You can also post your conf-file and post the last five lines from a
'vacuum analyze verbose'.
--
regards
Claus
When lenity and cruelty play for a kingdom,
the gentler gamester is the soonest winner.
Shakespeare
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grzegorz Jaśkiewicz | 2009-09-24 08:44:09 | Re: Speed while runnning large transactions. |
| Previous Message | jesper | 2009-09-24 08:27:46 | Speed while runnning large transactions. |