explain.depesz.com

PostgreSQL's explain analyze made readable

Result: 3VPE

Settings

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 72.698 2,291.673 ↓ 587.0 587 1

Gather Motion 20:1 (slice1; segments: 20) (cost=0.00..1,958.92 rows=1 width=9) (actual time=2,210.746..2,291.673 rows=587 loops=1)

  • (slice0) Executor memory: 135K bytes.
  • (slice1) Executor memory: 155K bytes avg x 20 workers, 164K bytes max (seg3).Memory used: 98304kBOptimizer: Pivotal Optimizer (GPORCA) version 3.88.0
2. 0.843 2,218.975 ↓ 43.0 43 1

Result (cost=0.00..1,958.92 rows=1 width=9) (actual time=2,218.915..2,218.975 rows=43 loops=1)

3. 2,218.132 2,218.132 ↓ 43.0 43 1

Seq Scan on container (cost=0.00..1,958.92 rows=1 width=30) (actual time=2,218.088..2,218.132 rows=43 loops=1)

  • Filter: ((im_origin_impc_code = 'HKHKGH'::text) AND (im_destination_impc_code = 'RUEKAA'::text) AND (date_part('year'::text, im_formation_date) = 2020::double precision) AND (im_category = 'C'::text) AND (im_formation_date >= '2020-01-01 11:37:08.421+00'::timestamp with time zone) AND (im_formation_date < '2020-12-21 11:37:08.421+00'::timestamp with time zone))
Planning time : 6.135 ms
Execution time : 2,303.385 ms