Re: Query plan with missing timespans

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Andomar <andomar(at)aule(dot)net>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Query plan with missing timespans
Date: 2015-04-22 19:47:03
Message-ID: 223706913.2307849.1429732023067.JavaMail.yahoo@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Andomar <andomar(at)aule(dot)net> wrote:

> In the output of "explain analyze" below, what was the query
> doing between actual time 1.426 and 17.077?

Looping through 384 index scans of tbl, each taking 0.040 ms.
That's 15.36 ms. That leaves 0.291 ms unaccounted for, which means
that's about how much time the top level nested loop took to do its
work.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andomar 2015-04-22 19:59:27 Re: Query plan with missing timespans
Previous Message Andomar 2015-04-22 17:37:49 Query plan with missing timespans