explain.depesz.com

PostgreSQL's explain analyze made readable

Result: MLpl

Settings
# exclusive inclusive rows x rows loops node
1. 68,202.186 73,365.408 ↓ 0.0 0 1

Update on customerattribute m (cost=125,178.58..372,087.98 rows=49 width=140) (actual time=73,365.408..73,365.408 rows=0 loops=1)

2. 3,379.395 5,163.222 ↓ 44,582.4 2,184,539 1

Hash Join (cost=125,178.58..372,087.98 rows=49 width=140) (actual time=1,103.596..5,163.222 rows=2,184,539 loops=1)

  • Hash Cond: ((m.customernbr = wt.customernbr) AND (m.attributecd = wt.attributecd) AND ((m.contentvalue)::text = (wt.contentvalue)::text) AND (m.effectivestartdttm = wt.effectivestartdttm))
3. 680.474 680.474 ↓ 1.0 2,184,539 1

Seq Scan on customerattribute m (cost=0.00..120,144.12 rows=2,170,312 width=130) (actual time=0.006..680.474 rows=2,184,539 loops=1)

  • Filter: currentrecord
4. 659.278 1,103.353 ↓ 1.0 2,184,539 1

Hash (cost=62,291.86..62,291.86 rows=2,184,386 width=48) (actual time=1,103.353..1,103.353 rows=2,184,539 loops=1)

  • Buckets: 65536 Batches: 64 Memory Usage: 3315kB
5. 444.075 444.075 ↓ 1.0 2,184,539 1

Seq Scan on customerattribute_wt wt (cost=0.00..62,291.86 rows=2,184,386 width=48) (actual time=0.004..444.075 rows=2,184,539 loops=1)

Planning time : 0.730 ms