explain.depesz.com

PostgreSQL's explain analyze made readable

Result: l13y

Settings
# exclusive inclusive rows x rows loops node
1. 52,207.336 57,364.785 ↓ 0.0 0 1

Update on customerattribute m (cost=125,178.58..373,784.99 rows=49 width=140) (actual time=57,364.785..57,364.785 rows=0 loops=1)

2. 3,372.646 5,157.449 ↓ 44,582.4 2,184,539 1

Hash Join (cost=125,178.58..373,784.99 rows=49 width=140) (actual time=1,138.401..5,157.449 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. 646.748 646.748 ↑ 1.0 2,184,539 1

Seq Scan on customerattribute m (cost=0.00..120,433.03 rows=2,198,703 width=130) (actual time=0.112..646.748 rows=2,184,539 loops=1)

  • Filter: currentrecord
4. 692.056 1,138.055 ↓ 1.0 2,184,539 1

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

  • Buckets: 65536 Batches: 64 Memory Usage: 3315kB
5. 445.999 445.999 ↓ 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.005..445.999 rows=2,184,539 loops=1)