Re: Meaning of "loops" in EXPLAIN ANALYSE output

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Aaron Bingham <bingham(at)cenix-bioscience(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Meaning of "loops" in EXPLAIN ANALYSE output
Date: 2006-04-10 15:48:07
Message-ID: 26412.1144684087@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Aaron Bingham <bingham(at)cenix-bioscience(dot)com> writes:
> For example, my EXPLAIN ANALYSE output contains the following line:

> Unique (cost=9775.21..10015.32 rows=1 width=8) (actual
> time=264.889..264.889 rows=1 loops=791)

> Does that mean that the entire operation took 264.889 ms, or that a
> single iteration took that long?

That's the average time per full execution cycle of the node, ie, we
actually spent 264.889 * 791 msec here or in its subnodes. Presumably
this node is in a subquery, or on the inside of a nestloop, or something
else that would demand its output more than once.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2006-04-10 16:14:10 Re: pg_restore 7.4.7 locks itself out
Previous Message Tom Lane 2006-04-10 15:45:23 Re: pg_restore 7.4.7 locks itself out