From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Checkpoint_segments optimal value |
Date: | 2014-07-18 00:10:22 |
Message-ID: | 53C865EE.50803@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin 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 <http://account.id>,
> account.organization_id, run.application_id, work_unit.script,
> work_unit.id <http://work_unit.id>, work_unit.start_time, run.id
> <http://run.id>, work_unit.priority FROM work_unit, run, account
> WHERE work_unit.status = 3 AND work_unit.run_id = run.id
> <http://run.id> AND work_unit.type != 1 AND run.status = 1 AND
> run.account_id = account.id <http://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
From | Date | Subject | |
---|---|---|---|
Next Message | Prabhjot Sheena | 2014-07-18 00:36:36 | Re: Checkpoint_segments optimal value |
Previous Message | Prabhjot Sheena | 2014-07-18 00:01:51 | Re: Checkpoint_segments optimal value |
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2014-07-18 00:19:06 | Re: Windows Installation User account - Correct database for us |
Previous Message | Prabhjot Sheena | 2014-07-18 00:01:51 | Re: Checkpoint_segments optimal value |