Query plan with missing timespans - Mailing list pgsql-performance

From Andomar
Subject Query plan with missing timespans
Date
Msg-id 5537DC6D.2010300@aule.net
Whole thread Raw
Responses Re: Query plan with missing timespans  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-performance
This is a question about how to read "explain analyze".  I've anonymized
column names and table names.

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

Kind regards,
Andomar


  HashAggregate  (cost=862.02..862.62 rows=48 width=90) (actual
time=17.077..17.077 rows=0 loops=1)
    Group Key: col, col, col
    Buffers: shared hit=6018
    ->  Nested Loop  (cost=1.52..861.18 rows=48 width=90) (actual
time=17.077..17.077 rows=0 loops=1)
          Buffers: shared hit=6018
          ->  Nested Loop  (cost=1.09..26.74 rows=303 width=41) (actual
time=0.033..1.426 rows=384 loops=1)
                Buffers: shared hit=845
                ->  Index Scan using ind on tbl  (cost=0.42..8.44 rows=1
width=8) (actual time=0.010..0.011 rows=1 loops=1)
                      Index Cond: (col = 123)
                      Buffers: shared hit=4
                ->  Index Scan using ind on tbl (cost=0.67..18.28 rows=2
width=49) (actual time=0.020..1.325 rows=384 loops=1)
                      Index Cond: (col = col)
                      Filter: (col = 'value')
                      Rows Removed by Filter: 2720
                      Buffers: shared hit=841
          ->  Index Scan using index on tbl (cost=0.42..2.74 rows=1
width=57) (actual time=0.040..0.040 rows=0 loops=384)
                Index Cond: (col = col)
                Filter: (col = ANY (ARRAY[func('value1'::text),
func('value2'::text)]))
                Rows Removed by Filter: 1
                Buffers: shared hit=5173
  Planning time: 0.383 ms
  Execution time: 17.128 ms


Version: PostgreSQL 9.4.1 on x86_64-unknown-linux-gnu, compiled by gcc
(GCC) 4.4.7 20120313 (Red Hat 4.4.7-11), 64-bit



pgsql-performance by date:

Previous
From: Jim Nasby
Date:
Subject: Re: extract(year from date) doesn't use index but maybe could?
Next
From: Kevin Grittner
Date:
Subject: Re: Query plan with missing timespans