explain.depesz.com

A tool for finding a real cause for slow queries.

Result: Gkt

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

Merge Join (cost=385093.26..402242.85 rows=1128213 width=446) (actual time=13527.907..20172.119 rows=1000000 loops=1)

  • Merge Cond: ((fs_debtitem.fs_party)::text = (fs_agrperson.fs_party)::text)
2. 641.129 1217.432 ↑ 1.8 28134 1

Sort (cost=91531.96..91661.51 rows=51822 width=66) (actual time=1171.080..1217.432 rows=28134 loops=1)

  • Sort Key: fs_debtitem.fs_party
  • Sort Method: quicksort Memory: 7048kB
3. 576.303 576.303 ↑ 1.1 45351 1

Seq Scan on fs_debtitem (cost=0.00..87473.96 rows=51822 width=66) (actual time=0.042..576.303 rows=45351 loops=1)

  • Filter: (fs_annualize = 0)
4. 7405.462 14227.440 ↓ 1.0 1000000 1

Sort (cost=293560.74..296029.08 rows=987333 width=380) (actual time=12239.873..14227.440 rows=1000000 loops=1)

  • Sort Key: fs_agrperson.fs_party
  • Sort Method: external sort Disk: 316568kB
5. 4050.368 6821.978 ↓ 1.0 1000000 1

Hash Join (cost=2358.40..195256.06 rows=987333 width=380) (actual time=381.338..6821.978 rows=1000000 loops=1)

  • Hash Cond: ((cm_ledgeritem.salesteam)::text = (fs_agrperson.tril_gid)::text)
6. 2574.895 2574.895 ↓ 1.0 1000000 1

Seq Scan on cm_ledgeritem (cost=0.00..173151.00 rows=987333 width=347) (actual time=184.581..2574.895 rows=1000000 loops=1)

  • Filter: (fs_batchid = 1)
7. 88.029 196.715 ↑ 1.0 45351 1

Hash (cost=1791.51..1791.51 rows=45351 width=66) (actual time=196.715..196.715 rows=45351 loops=1)

8. 108.686 108.686 ↑ 1.0 45351 1

Seq Scan on fs_agrperson (cost=0.00..1791.51 rows=45351 width=66) (actual time=0.009..108.686 rows=45351 loops=1)