explain.depesz.com

A tool for finding a real cause for slow queries.

Result: jxm

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 11,739.433 12,494.520 ↑ 1.0 1,000,000 1

Sort (cost=332,686.74..335,186.74 rows=1,000,000 width=99) (actual time=12,272.760..12,494.520 rows=1,000,000 loops=1)

  • Sort Key: tmp_ap_di.fs_party
  • Sort Method: external sort Disk: 106552kB
2. 520.659 755.087 ↑ 1.0 1,000,000 1

Hash Join (cost=2,473.40..68,966.40 rows=1,000,000 width=99) (actual time=32.973..755.087 rows=1,000,000 loops=1)

  • Hash Cond: ((tmp_cm_ledgeritem.salesteam)::text = (tmp_ap_di.ap_tril_gid)::text)
3. 201.491 201.491 ↑ 1.0 1,000,000 1

Seq Scan on tmp_cm_ledgeritem (cost=0.00..22,346.00 rows=1,000,000 width=66) (actual time=0.014..201.491 rows=1,000,000 loops=1)

4. 23.237 32.937 ↑ 1.0 45,351 1

Hash (cost=1,197.51..1,197.51 rows=45,351 width=99) (actual time=32.937..32.937 rows=45,351 loops=1)

5. 9.700 9.700 ↑ 1.0 45,351 1

Seq Scan on tmp_ap_di (cost=0.00..1,197.51 rows=45,351 width=99) (actual time=0.008..9.700 rows=45,351 loops=1)