Re: Checkpoint_segments optimal value - Mailing list pgsql-general

From John R Pierce
Subject Re: Checkpoint_segments optimal value
Date
Msg-id 53C86017.7020903@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 4:26 PM, Prabhjot Sheena wrote:
Here is the explain plan. There query time went backup up to 2 to 3 minutes from 3 second  in just 2 hrs.  Can anyone suggest something on how to fix this or why this is happening

 explain 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;

you need to use EXPLAIN ANALYZE to get accurate data.

run it when the query is fast, and again when the query is slow, paste both outputs here.   also, you can paste them to http://explain.depesz.com and that will give you a nice analysis of the timing data included in the EXPLAIN ANALYZE output.




-- 
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: John R Pierce
Date:
Subject: Re: Checkpoint_segments optimal value