Aaron Bingham <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
