Re: Postgres using the wrong index index

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Matt Dupree <matt(dot)dupree(at)heap(dot)io>
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres using the wrong index index
Date: 2021-08-12 03:45:11
Message-ID: 20210812034510.GG10479@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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.92 rows=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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Matt Dupree 2021-08-12 13:38:45 Re: Postgres using the wrong index index
Previous Message Mladen Gogala 2021-08-11 21:45:34 Re: Postgres using the wrong index index