July 1, 2026
SQL needs a hall monitor
Database Traffic Control
Postgres gets a traffic cop, and the comments instantly start fighting
TLDR: PlanetScale launched a feature that lets users cap and block runaway database requests before everything slows to a crawl. Commenters were split between cheers for the new safety net and eye-rolls from veterans saying paid database systems have had this kind of crowd control for ages.
PlanetScale just unveiled Database Traffic Control, a new tool meant to stop a database from melting down when one bad actor — think a buggy feature, overeager background job, or sudden AI frenzy — starts hogging all the attention. In plain English: it lets companies put limits on which app requests get to eat up precious database power, so the important stuff keeps working. You can watch in a warning mode first, then flip the switch and start blocking the greedy troublemakers for real.
But the real show was in the comments, where the crowd split into familiar internet factions almost immediately. One side was basically saying, "finally, someone put a bouncer at the club door". The lead engineer even popped into the thread like a proud parent, dropping a behind-the-scenes explainer and offering to answer questions — a move that gave the launch a very "come at me, I brought receipts" energy.
Then came the skeptics. One commenter unloaded a full shopping list of things they think Postgres still handles badly, arguing this solves one pain point while bigger structural headaches remain. Another cut straight to the wallet-drama: this is the kind of feature you get when you "pay the man," pointing to big commercial databases that have offered similar controls for years. The mood? Equal parts impressed, suspicious, and darkly amused that modern databases apparently need traffic cops, class systems, and crowd control just to survive the apps we keep throwing at them.
Key Points
- •PlanetScale launched Database Traffic Control for PlanetScale Postgres to let users set resource budgets on database query traffic.
- •The feature can match query subsets by query pattern, application name, Postgres user, or custom tags attached through SQL comments.
- •Users can cap resources including CPU percentage, CPU burst, backend process concurrency, and per-query timing.
- •Budgets support both warn mode for observation and enforce mode for active blocking of queries that exceed limits.
- •PlanetScale says the feature is available now for all PlanetScale Postgres databases through Insights, API, and CLI, with support for automation and multi-tenant traffic prioritization.