how to identify expensive steps in an explain analyze output - Mailing list pgsql-performance

From Frits Hoogland
Subject how to identify expensive steps in an explain analyze output
Date
Msg-id fbb8fbcd0802270354g3b80e90bgfeaa3bf6536cabb3@mail.gmail.com
Whole thread Raw
In response to how to identify expensive steps in an explain analyze output  ("Frits Hoogland" <frits.hoogland@gmail.com>)
Responses Re: how to identify expensive steps in an explain analyze output
List pgsql-performance

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

pgsql-performance by date:

Previous
From: "Frits Hoogland"
Date:
Subject: how to identify expensive steps in an explain analyze output
Next
From: Tom Lane
Date:
Subject: Re: how to identify expensive steps in an explain analyze output