explain.depesz.com

A tool for finding a real cause for slow queries.

Result: Y8T

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 25,299.415 319,820.095 ↑ 1.1 1,780,334 1

Sort (cost=999,045.98..1,003,820.42 rows=1,909,775 width=59) (actual time=316,664.105..319,820.095 rows=1,780,334 loops=1)

  • Output: mondetails_recent.serverid, mondetails_recent.vmid, mondetails_recent.sv1, (todecimal(mondetails_recent.sv1))
  • Sort Key: (todecimal(mondetails_recent.sv1))
  • Sort Method: quicksort Memory: 161149kB
2. 28,177.867 294,520.680 ↑ 1.1 1,780,334 1

Hash Semi Join (cost=1.30..799,808.98 rows=1,909,775 width=59) (actual time=91.779..294,520.680 rows=1,780,334 loops=1)

  • Output: mondetails_recent.serverid, mondetails_recent.vmid, mondetails_recent.sv1, todecimal(mondetails_recent.sv1)
  • Hash Cond: ((mondetails_recent.serverid)::text = (hosts.guid)::text)
3. 266,342.732 266,342.732 ↑ 1.1 1,780,334 1

Seq Scan on public.mondetails_recent (cost=0.00..296,104.52 rows=1,909,775 width=59) (actual time=24.647..266,342.732 rows=1,780,334 loops=1)

  • Output: mondetails_recent.mid, mondetails_recent.serverid, mondetails_recent.vmid, mondetails_recent.slapolicyguid, mondetails_recent.policyid
  • Filter: ((mondetails_recent.stime >= 1335848499) AND (mondetails_recent.mid = 1000))
4. 0.039 0.081 ↑ 1.0 12 1

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

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

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

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