Re: Postgres using the wrong index index

2021-08-23 Thread Matt Dupree
uery is for the > previous month (July). > > $ date -d @1530186399 > Thu Jun 28 06:46:39 CDT 2018 > $ date -d @1629125609 > Mon Aug 16 09:53:29 CDT 2021 > > $ date -d @1627369200 > Tue Jul 27 02:00:00 CDT 2021 > $ date -d @1624777200 > Sun Jun 27 02:00:00 CDT 2021 &

Re: Postgres using the wrong index index

2021-08-12 Thread Matt Dupree
s_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" >= > '162477720'::bigint) AND (other_ev

Postgres using the wrong index index

2021-08-11 Thread Matt Dupree
d history on why we have things set up this way here <https://heap.io/blog/running-10-million-postgresql-indexes-in-production>. Here's the table metadata for other_events_1004175222: SELECT relname, relpages, reltuples, relallvisible, relkind, relnatts, relhassubclass, reloptions, pg_table_size(oid) FROM pg_class WHERE relname = 'other_events_1004175222'; Results: [image: image.png] -- K. Matt Dupree Data Science Engineer 321.754.0526 | matt.dup...@heap.io