# When the Postgres query planner goes rogue

DevFeed: [When the Postgres query planner goes rogue](<https://devfeed.tech/articles/when-the-postgres-query-planner-goes-rogue-2344.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/when-the-postgres-query-planner-goes-rogue>)

Author: Nick Van Wiggeren

Published: 2026-07-13T00:00:00Z

Content type: article

Language: en

Sources: [Blog -- PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [cpu](<https://devfeed.tech/topics/cpu.md>)

Tags: [cpu](<https://devfeed.tech/tags/cpu.md>), [database](<https://devfeed.tech/tags/database.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [insights](<https://devfeed.tech/tags/insights.md>), [latency](<https://devfeed.tech/tags/latency.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [resource](<https://devfeed.tech/tags/resource.md>), [sql](<https://devfeed.tech/tags/sql.md>), [statistics](<https://devfeed.tech/tags/statistics.md>)

## AI overview

PlanetScale describes containing a runaway Postgres query whose planner choice caused severe latency and CPU saturation. A strict Database Traffic Control budget stopped further executions while the customer investigated the root cause.

## Source excerpt

How PlanetScale Database Traffic Control contained a runaway Postgres query after the planner abandoned an index.