explain.depesz.com

A tool for finding a real cause for slow queries.

Result: FcV

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.225 68,724.502 ↑ 75.1 24 1

Sort (cost=342,033.45..342,037.95 rows=1,802 width=63) (actual time=68,724.458..68,724.502 rows=24 loops=1)

  • Output: mondetails_recent.serverid, mondetails_recent.vmid, (max(todecimal(mondetails_recent.sv1))), mondetails_recent.mid
  • Sort Key: (max(todecimal(mondetails_recent.sv1)))
  • Sort Method: quicksort Memory: 20kB
2. 26,610.473 68,724.277 ↑ 75.1 24 1

HashAggregate (cost=341,462.98..341,936.00 rows=1,802 width=63) (actual time=68,724.215..68,724.277 rows=24 loops=1)

  • Output: mondetails_recent.serverid, mondetails_recent.vmid, max(todecimal(mondetails_recent.sv1)), mondetails_recent.mid
3. 11,134.325 42,113.804 ↑ 1.1 1,780,334 1

Hash Join (cost=1.30..322,365.23 rows=1,909,775 width=63) (actual time=12.942..42,113.804 rows=1,780,334 loops=1)

  • Output: mondetails_recent.serverid, mondetails_recent.vmid, mondetails_recent.sv1, mondetails_recent.mid
  • Hash Cond: ((mondetails_recent.serverid)::text = (hosts.guid)::text)
4. 30,979.403 30,979.403 ↑ 1.1 1,780,334 1

Seq Scan on public.mondetails_recent (cost=0.00..296,104.52 rows=1,909,775 width=63) (actual time=12.814..30,979.403 rows=1,780,334 loops=1)

  • Output: mondetails_recent.mid, mondetails_recent.serverid, mondetails_recent.vmid, mondetails_recent.slapolicyguid, mondetails_recent.po
  • Filter: ((mondetails_recent.stime >= 1335848499) AND (mondetails_recent.mid = 1000))
5. 0.035 0.076 ↑ 1.0 12 1

Hash (cost=1.15..1.15 rows=12 width=29) (actual time=0.076..0.076 rows=12 loops=1)

  • Output: hosts.guid
  • Buckets: 1024 Batches: 1 Memory Usage: 1kB
6. 0.041 0.041 ↑ 1.0 12 1

Seq Scan on public.hosts (cost=0.00..1.15 rows=12 width=29) (actual time=0.009..0.041 rows=12 loops=1)

  • Output: hosts.guid
  • Filter: (hosts.hosttype <> 3)