explain.depesz.com

A tool for finding a real cause for slow queries.

Result: KEz

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

Limit (cost=0.00..34,344.83 rows=500,000 width=99) (actual time=0.080..1,640.894 rows=500,000 loops=1)

2. 1,456.057 1,588.699 ↑ 1,998,932.3 500,000 1

Merge Join (cost=0.00..68,652,998,770.25 rows=999,466,157,905 width=99) (actual time=0.078..1,588.699 rows=500,000 loops=1)

  • Merge Cond: ((tmp_ap_di.ap_tril_gid)::text = (tmp_cm_ledgeritem.salesteam)::text)
3. 0.042 0.042 ↑ 1,999,999.0 1 1

Index Scan using tmp_ap_di_ap_tril_gid on tmp_ap_di (cost=0.00..254,613.18 rows=1,999,999 width=99) (actual time=0.042..0.042 rows=1 loops=1)

4. 132.600 132.600 ↑ 2.0 500,000 1

Index Scan using tmp_cm_ledgeritem_salesteam on tmp_cm_ledgeritem (cost=0.00..56,189.54 rows=1,000,000 width=66) (actual time=0.026..132.600 rows=500,000 loops=1)