pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed From: John R Pierce <pierce@hogranch.com>
To: pgsql-general@postgresql.org
Subject: Re: Checkpoint_segments optimal value
Date: Thu, 17 Jul 2014 16:45:27 -0700
Message-ID: <53C86017.7020903@hogranch.com> (raw )
In-Reply-To: <CAOf_bQbFEM6oT24sLrpw+-LKHGXvR=VomFQH7GSGV0jVtrCLOg@mail.gmail.com >
References: <CAOf_bQYehfKp7CNRa_pYQ+-SmHyDSYJ8bddbaixXUcWmSjH6wA@mail.gmail.com >
<20140717140103.4e8c05e8ef5b89817b4d160a@potentialtech.com >
<7639.1405620388@sss.pgh.pa.us >
<CAOf_bQaRBDorZnjhBqM451mmsorac=9LSGP0b5ZNkUP9heo+OQ@mail.gmail.com >
<20140717150035.6822faed729cbd871edcc5ad@potentialtech.com >
<CAOf_bQbFEM6oT24sLrpw+-LKHGXvR=VomFQH7GSGV0jVtrCLOg@mail.gmail.com >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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 <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 ;;
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
view thread (19+ messages) latest in thread
Message-ID: <53C86017.7020903@hogranch.com>
Permalink: ../53C86017.7020903@hogranch.com/
Also on: postgresql.org/message-id/53C86017.7020903@hogranch.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pierce@hogranch.com, pgsql-general@postgresql.org
Subject: Re: Checkpoint_segments optimal value
In-Reply-To: <53C86017.7020903@hogranch.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox