explain.depesz.com

A tool for finding a real cause for slow queries.

Result: Gmv

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 13,412.970 32,765.282 ↑ 104.6 1,000,000 1

Sort (cost=203,264,758.08..203,526,286.39 rows=104,611,325 width=672) (actual time=32,233.563..32,765.282 rows=1,000,000 loops=1)

  • Sort Key: tmp_ap_di.fs_party
  • Sort Method: external sort Disk: 339208kB
2. 4,345.318 19,352.312 ↑ 104.6 1,000,000 1

Merge Join (cost=1,110,470.14..2,684,870.00 rows=104,611,325 width=672) (actual time=14,331.078..19,352.312 rows=1,000,000 loops=1)

  • Merge Cond: ((cm_ledgeritem.salesteam)::text = (tmp_ap_di.ap_tril_gid)::text)
3. 13,156.307 14,071.737 ↑ 1.0 1,000,000 1

Sort (cost=1,105,457.98..1,107,968.82 rows=1,004,333 width=500) (actual time=13,471.694..14,071.737 rows=1,000,000 loops=1)

  • Sort Key: cm_ledgeritem.salesteam
  • Sort Method: external sort Disk: 275664kB
4. 915.430 915.430 ↑ 1.0 1,000,000 1

Seq Scan on cm_ledgeritem (cost=0.00..99,075.00 rows=1,004,333 width=500) (actual time=0.009..915.430 rows=1,000,000 loops=1)

  • Filter: (fs_batchid = 1)
5. 109.480 935.257 ↓ 49.4 1,029,899 1

Materialize (cost=5,012.15..5,272.55 rows=20,832 width=258) (actual time=707.158..935.257 rows=1,029,899 loops=1)

6. 814.610 825.777 ↓ 1.4 29,900 1

Sort (cost=5,012.15..5,064.23 rows=20,832 width=258) (actual time=707.153..825.777 rows=29,900 loops=1)

  • Sort Key: tmp_ap_di.ap_tril_gid
  • Sort Method: external merge Disk: 4808kB
7. 11.167 11.167 ↓ 2.2 45,351 1

Seq Scan on tmp_ap_di (cost=0.00..952.32 rows=20,832 width=258) (actual time=0.013..11.167 rows=45,351 loops=1)