Re: Postgres using the wrong index index

The rowcount estimate for the time column is bad for all these plans - do you
know why ?  You're using inheritence - have you analyzed the parent tables
recently ?

| Index Scan using other_events_1004175222_pim_evdef_67951aef14bc_idx on public.other_events_1004175222
(cost=0.28..1,648,877.92rows=1,858,891 width=32) (actual time=1.008..15.245 rows=23 loops=1)
 
|    Index Cond: ((other_events_1004175222."time" >= '1624777200000'::bigint) AND (other_events_1004175222."time" <=
'1627369200000'::bigint))

-- 
Justin