explain.depesz.com

A tool for finding a real cause for slow queries.

Result: A0n

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 630.995 1,303.983 ↑ 1.1 1,381 1

HashAggregate (cost=43,134.82..43,149.84 rows=1,502 width=12) (actual time=1,303.735..1,303.983 rows=1,381 loops=1)

2. 209.115 672.988 ↑ 1.0 836,971 1

Hash Join (cost=139.13..38,949.97 rows=836,971 width=12) (actual time=5.243..672.988 rows=836,971 loops=1)

  • Hash Cond: (lpc.corpus_id_ = c.id_)
3. 324.420 460.349 ↑ 1.0 836,971 1

Hash Join (cost=45.41..26,301.68 rows=836,971 width=20) (actual time=1.694..460.349 rows=836,971 loops=1)

  • Hash Cond: (lpc.pair_id_ = lp.id_)
4. 134.276 134.276 ↑ 1.0 836,971 1

Seq Scan on letterpairs_corpuses lpc (cost=0.00..13,701.71 rows=836,971 width=24) (actual time=0.011..134.276 rows=836,971 loops=1)

5. 0.942 1.653 ↑ 1.0 1,618 1

Hash (cost=25.18..25.18 rows=1,618 width=12) (actual time=1.653..1.653 rows=1,618 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 76kB
6. 0.711 0.711 ↑ 1.0 1,618 1

Seq Scan on letterpairs lp (cost=0.00..25.18 rows=1,618 width=12) (actual time=0.009..0.711 rows=1,618 loops=1)

7. 1.246 3.524 ↑ 1.0 2,429 1

Hash (cost=63.36..63.36 rows=2,429 width=8) (actual time=3.524..3.524 rows=2,429 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 95kB
8. 2.278 2.278 ↑ 1.0 2,429 1

Seq Scan on corpuses c (cost=0.00..63.36 rows=2,429 width=8) (actual time=0.010..2.278 rows=2,429 loops=1)

  • Filter: (name_ = 'main'::text)