explain.depesz.com

A tool for finding a real cause for slow queries.

Result: y0q

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.020 0.098 ↓ 2.0 2 1

Sort (cost=24.51..24.51 rows=1 width=1148) (actual time=0.096..0.098 rows=2 loops=1)

  • Sort Key: (upper((u.name)::text))
  • Sort Method: quicksort Memory: 17kB
2. 0.033 0.078 ↓ 2.0 2 1

Hash Join (cost=13.66..24.50 rows=1 width=1148) (actual time=0.061..0.078 rows=2 loops=1)

  • Hash Cond: ((u.id)::text = (uc.user_id)::text)
3. 0.016 0.016 ↑ 8.6 7 1

Seq Scan on "user" u (cost=0.00..10.60 rows=60 width=1148) (actual time=0.009..0.016 rows=7 loops=1)

4. 0.008 0.029 ↑ 1.0 2 1

Hash (cost=13.64..13.64 rows=2 width=82) (actual time=0.029..0.029 rows=2 loops=1)

5. 0.010 0.021 ↑ 1.0 2 1

Bitmap Heap Scan on user_company uc (cost=9.40..13.64 rows=2 width=82) (actual time=0.019..0.021 rows=2 loops=1)

  • Recheck Cond: ((company_id)::text = 'c3a1c8e4cb654a6a891c74ac49c13988'::text)
6. 0.011 0.011 ↑ 1.0 2 1

Bitmap Index Scan on user_company_pk (cost=0.00..9.40 rows=2 width=0) (actual time=0.011..0.011 rows=2 loops=1)

  • Index Cond: ((company_id)::text = 'c3a1c8e4cb654a6a891c74ac49c13988'::text)