explain.depesz.com

A tool for finding a real cause for slow queries.

Result: mMY

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

Unique (cost=12.56..12.58 rows=1 width=706) (actual time=0.210..0.226 rows=2 loops=1)

2. 0.099 0.210 ↓ 4.0 4 1

Sort (cost=12.56..12.56 rows=1 width=706) (actual time=0.206..0.210 rows=4 loops=1)

  • Sort Key: t.id, t.name, t.description, t.initial_period, t.initial_period_cost, t.billing_period, t.billing_period_aggregated, t.billing_period_aggregated_cost
  • Sort Method: quicksort Memory: 18kB
3. 0.022 0.111 ↓ 4.0 4 1

Nested Loop (cost=0.00..12.55 rows=1 width=706) (actual time=0.057..0.111 rows=4 loops=1)

4. 0.045 0.045 ↓ 4.0 4 1

Index Scan using co_app_trf_pk on company_applicability_tariff cat (cost=0.00..6.27 rows=1 width=82) (actual time=0.039..0.045 rows=4 loops=1)

  • Index Cond: ((company_id)::text = 'c3a1c8e4cb654a6a891c74ac49c13988'::text)
5. 0.044 0.044 ↑ 1.0 1 4

Index Scan using tariff_pk on tariff t (cost=0.00..6.27 rows=1 width=706) (actual time=0.010..0.011 rows=1 loops=4)

  • Index Cond: ((t.id)::text = (cat.tariff_id)::text)