explain.depesz.com

A tool for finding a real cause for slow queries.

Result: ni9r

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.009 0.065 ↑ 53.5 2 1

HashAggregate (cost=88.41..89.48 rows=107 width=8) (actual time=0.064..0.065 rows=2 loops=1)

2. 0.007 0.056 ↑ 35.7 3 1

Nested Loop (cost=15.01..87.87 rows=107 width=8) (actual time=0.039..0.056 rows=3 loops=1)

3. 0.012 0.037 ↑ 35.7 3 1

Hash Join (cost=15.01..55.50 rows=107 width=8) (actual time=0.033..0.037 rows=3 loops=1)

  • Hash Cond: (badgegroups_to_topiccategories.category_id = user_topiccategories_counters.category_id)
4. 0.008 0.008 ↑ 713.3 3 1

Seq Scan on badgegroups_to_topiccategories (cost=0.00..31.40 rows=2140 width=8) (actual time=0.006..0.008 rows=3 loops=1)

5. 0.003 0.017 ↑ 3.3 3 1

Hash (cost=14.88..14.88 rows=10 width=8) (actual time=0.017..0.017 rows=3 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 1kB
6. 0.006 0.014 ↑ 3.3 3 1

Bitmap Heap Scan on user_topiccategories_counters (cost=4.33..14.88 rows=10 width=8) (actual time=0.012..0.014 rows=3 loops=1)

  • Recheck Cond: (user_id = 500000)
7. 0.008 0.008 ↑ 3.3 3 1

Bitmap Index Scan on counters_pkey (cost=0.00..4.33 rows=10 width=0) (actual time=0.008..0.008 rows=3 loops=1)

  • Index Cond: (user_id = 500000)
8. 0.012 0.012 ↑ 1.0 1 3

Index Scan using badgegroups_pkey on badgegroups (cost=0.00..0.29 rows=1 width=4) (actual time=0.003..0.004 rows=1 loops=3)

  • Index Cond: (badgegroup_id = badgegroups_to_topiccategories.badgegroup_id)