From: | jesper(at)krogh(dot)cc |
---|---|
To: | Grzegorz JaÅkiewicz <gryzman(at)gmail(dot)com> |
Cc: | jesper(at)krogh(dot)cc, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Speed while runnning large transactions. |
Date: | 2009-09-24 11:39:30 |
Message-ID: | 92e7ed8327b674f57e75f6307bdcf305.squirrel@shrek.krogh.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> On Thu, Sep 24, 2009 at 9:27 AM, <jesper(at)krogh(dot)cc> wrote:
>
>> Hi.
>>
>> 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?
>>
>> show us explain from the query(s).
> use select * from pg_stat_activity to find out the state query is in, and
> perhaps which one of the queries it really is.
I'm actively monitoring pg_stat_activity for potential problems but the
thread is spending most of the time in the application side. The
transaction is holding a large set of inserts/update and delete for the
DB.
--
Jesper
From | Date | Subject | |
---|---|---|---|
Next Message | Jared Beck | 2009-09-24 12:22:52 | Re: Slow query after upgrade to 8.4 |
Previous Message | jesper | 2009-09-24 11:35:48 | Re: Speed while runnning large transactions. |