how to identify expensive steps in an explain analyze output

From: "Frits Hoogland" <frits(dot)hoogland(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: how to identify expensive steps in an explain analyze output
Date: 2008-02-27 11:54:01
Message-ID: fbb8fbcd0802270354g3b80e90bgfeaa3bf6536cabb3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2008-02-27 15:26:07 Re: how to identify expensive steps in an explain analyze output
Previous Message Frits Hoogland 2008-02-27 10:18:25 how to identify expensive steps in an explain analyze output