From: Frits Hoogland <frits.hoogland@gmail.com>
To: pgsql-performance@postgresql.org
Subject: how to identify expensive steps in an explain analyze output
Date: Wed, 27 Feb 2008 12:54:01 +0100
Message-ID: <fbb8fbcd0802270354g3b80e90bgfeaa3bf6536cabb3@mail.gmail.com> (raw)
In-Reply-To: <fbb8fbcd0802270218u3d27c829y5f615250e9786a61@mail.gmail.com>
References: <fbb8fbcd0802270218u3d27c829y5f615250e9786a61@mail.gmail.com>
I've got some long running queries, and want to tune them.
Using simple logic, I can understand what expensive steps in the query plan
ought to be (seq scan and index scans using much rows), but I want to
quantify; use a somewhat more scientific approach.
The manual states: "Actually two numbers are shown: the start-up time before
the first row can be returned, and the total time to return all the rows.".
Does this mean that the difference between the first and second is the cost
or the time the step in the explain has taken?
TIA
frits
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-performance@postgresql.org
Cc: frits.hoogland@gmail.com
Subject: Re: how to identify expensive steps in an explain analyze output
In-Reply-To: <fbb8fbcd0802270354g3b80e90bgfeaa3bf6536cabb3@mail.gmail.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