Re: Checkpoint_segments optimal value - Mailing list pgsql-general

From John R Pierce
Subject Re: Checkpoint_segments optimal value
Date
Msg-id 53C865EE.50803@hogranch.com
Whole thread Raw
In response to Re: Checkpoint_segments optimal value  (Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>)
Responses Re: Checkpoint_segments optimal value  (Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>)
List pgsql-general
On 7/17/2014 5:01 PM, Prabhjot Sheena wrote:
i just did explain analyze and currently database is running slow coz of the query

explain ANALYZE SELECT account.id, account.organization_id, run.application_id, work_unit.script, work_unit.id, work_unit.start_time, run.id, work_unit.priority  FROM work_unit, run, account  WHERE  work_unit.status = 3 AND work_unit.run_id = run.id AND work_unit.type != 1 AND run.status = 1 AND run.account_id = account.id;

what does the overall workload on the system look like when this is so slow?   taking over a minute to do 1820 iterations of a 3138 row index scan seems way out of bounds for anything other than a very heavily overloaded server.

is this running on a virtual machine where there are other virtual servers contending for the same resources ?

btw, here's your analyze formatted pretty:  http://explain.depesz.com/s/XRI



-- 
john r pierce                                      37N 122W
somewhere on the middle of the left coast

pgsql-general by date:

Previous
From: Prabhjot Sheena
Date:
Subject: Re: Checkpoint_segments optimal value
Next
From: Adrian Klaver
Date:
Subject: Re: Windows Installation User account - Correct database for us