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 iter
On Mon, Apr 10, 2006 at 04:08:01PM +0100, Richard Huxton wrote:
> Aaron Bingham wrote:
> >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 lon
Aaron Bingham wrote:
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? The time for the entire query would
suggest the latter interpretation
Y
Hi,
I have a query optimization problem and I have failed to find the part
of the Postgres docs that explains the meaning of the "loops" value in
the EXPLAIN ANALYSE output.
For example, my EXPLAIN ANALYSE output contains the following line:
Unique (cost=9775.21..10015.32 rows=1 width=8) (a
