---
title: "Discussion on \"Query Planning Overhead with Many Chunks (And How to Fix It)\" | Hashnode"
description: "Discussion on \"Query Planning Overhead with Many Chunks (And How to Fix It)\". The Hidden Cost of TimescaleDB Chunks: Query Planning Time\nI spent an entire afternoon trying to figure out why a trivial aggregation query was taking 500ms on a well-indexed TimescaleDB hypertable. EXPLAIN ANALYZE showed 2ms of execution. The indexe..."
url: "https://hashnode.com/posts/query-planning-overhead-with-many-chunks-and-how-to-fix-it/69b28ea29404280c14870585"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Query Planning Overhead with Many Chunks (And How to Fix It)](https://postgresdba.hashnode.dev/query-planning-overhead-with-many-chunks-and-how-to-fix-it?utm_source=hashnode&utm_medium=feed)

The Hidden Cost of TimescaleDB Chunks: Query Planning Time I spent an entire afternoon trying to figure out why a trivial aggregation query was taking 500ms on a well-indexed TimescaleDB hypertable. EXPLAIN ANALYZE showed 2ms of execution. The indexe...

Mar 12 · 4 min read · postgresdba.hashnode.dev  
Read the article

-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#timescaledb](https://hashnode.com/tag/timescaledb)
-   [#database](https://hashnode.com/tag/database)

## Written by

[Philip McClarence](https://hashnode.com/@pgdba)

@pgdba · London, UK

  
[View profile](https://hashnode.com/@pgdba)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
