explain.depesz.com

A tool for finding a real cause for slow queries.

Result: keh

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 20897.722 21022.330 ↑ 1.0 106315 1

Hash Right Join (cost=3295.88..97365.40 rows=106315 width=23) (actual time=162.339..21022.330 rows=106315 loops=1)

  • Hash Cond: ((retail_tb_customer.customerno)::text = (a.user_id)::text)
  • -> Seq Scan on retail_tb_customer (cost=0.00..79963.40 rows=1251140 width=23) (actual time=8.258..19223.605 rows=1257207
2. 124.608 124.608 ↑ 1.0 106315 1

Hash (cost=1966.94..1966.94 rows=106315 width=12) (actual time=124.608..124.608 rows=106315 loops=1)

  • Buckets: 16384 Batches: 1 Memory Usage: 4621kB
  • -> Seq Scan on tmp_log_node_29006 a (cost=0.00..1966.94 rows=106315 width=12) (actual time=13.060..73.340 rows=106
  • Filter: (control_group_type = 1::numeric)