explain.depesz.com

PostgreSQL's explain analyze made readable

Result: inPg : Optimization for: plan #e8cv

Settings

Optimization path:

# exclusive inclusive rows x rows loops node
1. 13.486 23,395.496 ↑ 3.6 6,265 1

Sort (cost=422,578.36..422,634.29 rows=22,372 width=4) (actual time=23,394.104..23,395.496 rows=6,265 loops=1)

  • Sort Key: i0_.oid
  • Sort Method: quicksort Memory: 486kB
2. 2,068.540 23,382.010 ↑ 3.6 6,265 1

Hash Join (cost=181,339.08..420,962.05 rows=22,372 width=4) (actual time=13,710.172..23,382.010 rows=6,265 loops=1)

  • Hash Cond: (i0_.id_releve = i1_.rid)
3. 7,603.733 7,603.733 ↑ 1.0 4,124,641 1

Seq Scan on vm_requeteur_observations i0_ (cost=0.00..187,838.00 rows=4,124,900 width=8) (actual time=0.011..7,603.733 rows=4,124,641 loops=1)

4. 5.478 13,709.737 ↑ 5.7 2,960 1

Hash (cost=181,126.49..181,126.49 rows=17,007 width=4) (actual time=13,709.737..13,709.737 rows=2,960 loops=1)

  • Buckets: 2048 Batches: 1 Memory Usage: 105kB
5. 760.690 13,704.259 ↑ 5.7 2,960 1

Hash Join (cost=35.65..181,126.49 rows=17,007 width=4) (actual time=19.732..13,704.259 rows=2,960 loops=1)

  • Hash Cond: (i1_.id_jdd = i2_.id_jdd)
6. 12,943.528 12,943.528 ↑ 1.0 2,084,695 1

Seq Scan on vm_requeteur_releves i1_ (cost=0.00..173,101.74 rows=2,085,074 width=8) (actual time=0.009..12,943.528 rows=2,084,695 loops=1)

7. 0.006 0.041 ↑ 1.0 10 1

Hash (cost=35.53..35.53 rows=10 width=4) (actual time=0.041..0.041 rows=10 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 1kB
8. 0.035 0.035 ↑ 1.0 10 1

Index Scan using jdd_id_ca_idx on jdd i2_ (cost=0.28..35.53 rows=10 width=4) (actual time=0.017..0.035 rows=10 loops=1)

  • Index Cond: (id_ca = 451)
Total runtime : 23,396.306 ms