explain.depesz.com

A tool for finding a real cause for slow queries.

Result: cfN

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 13643.445 15637.335 ↓ 1.1 1000000 1

Sort (cost=1370778.50..1373058.41 rows=911963 width=599) (actual time=15095.219..15637.335 rows=1000000 loops=1)

  • Sort Key: fs_agrperson.fs_party
  • Sort Method: external sort Disk: 371464kB
2. 617.511 1993.890 ↓ 1.1 1000000 1

Hash Join (cost=93996.64..307976.48 rows=911963 width=599) (actual time=560.225..1993.890 rows=1000000 loops=1)

  • Hash Cond: ((cm_ledgeritem.salesteam)::text = (fs_agrperson.tril_gid)::text)
3. 816.220 816.220 ↑ 1.0 1000000 1

Index Scan using tmp_idx on cm_ledgeritem (cost=0.00..65801.30 rows=1004333 width=500) (actual time=0.045..816.220 rows=1000000 loops=1)

  • Index Cond: (fs_batchid = 1)
4. 26.734 560.159 ↓ 1.1 45351 1

Hash (cost=92676.89..92676.89 rows=41180 width=132) (actual time=560.159..560.159 rows=45351 loops=1)

5. 54.811 533.425 ↓ 1.1 45351 1

Hash Join (cost=2886.40..92676.89 rows=41180 width=132) (actual time=57.446..533.425 rows=45351 loops=1)

  • Hash Cond: ((fs_debtitem.fs_party)::text = (fs_agrperson.fs_party)::text)
6. 421.295 421.295 ↓ 1.1 45351 1

Seq Scan on fs_debtitem (cost=0.00..87468.89 rows=41180 width=66) (actual time=0.011..421.295 rows=45351 loops=1)

  • Filter: (fs_annualize = 0)
7. 21.074 57.319 ↑ 1.0 45351 1

Hash (cost=1787.51..1787.51 rows=45351 width=66) (actual time=57.319..57.319 rows=45351 loops=1)

8. 36.245 36.245 ↑ 1.0 45351 1

Seq Scan on fs_agrperson (cost=0.00..1787.51 rows=45351 width=66) (actual time=0.007..36.245 rows=45351 loops=1)