Hi everyone,
I recently encountered an issue where TimescaleDB’s query planner is not using an index I created on a hypertable. The table contains millions of rows & I expected my queries to benefit from indexing, but EXPLAIN ANALYZE shows that the planner is opting for a sequential scan instead. Image may be NSFW.
Clik here to view.
I hav checked index type (e.g., B-tree vs. BRIN) to ensure it’s suitable for my query patterns.
Ran ANALYZE and VACUUM to update statistics. Forced index usage using SET enable_seqscan TO off; which speeds up the query, but I don’t want to rely on manual overrides. Image may be NSFW.
Clik here to view.
Checked Timescale Documentation | Troubleshooting queriesMlops Course guide related to this and found it quite informative.
Has anyone else faced this issue? Could it be related to TimescaleDB’s chunking mechanism affecting query planning? Any insights on why PostgreSQL/TimescaleDB might ignore an index even when it seems optimal? Image may be NSFW.
Clik here to view.
Thank you!! Image may be NSFW.
Clik here to view.
2 posts - 2 participants
