Blog
Simeon Griggs [@simeonGriggs] |
Deadlocks happen when transactions block each other. Learn how they escalate into downtime, how to reduce them through better queries and retry logic, and how Traffic Control can protect your database from your application. →
Simeon Griggs [@simeonGriggs] |
Yo, I heard you liked databases, so we put logical databases in your database cluster so you can database while you database →
Tom Pang |
Large DELETEs add work instead of reclaiming it. Structure your database so deletion becomes DROP TABLE or TRUNCATE. →
Simeon Griggs [@simeonGriggs] |
Reducing the size and frequency of requests to your database has the double benefit of making your applications faster and cheaper. →
Simeon Griggs [@simeonGriggs] |
The best way for you and your agents to see how your database actually performs in production. →
Josh Brown [@imjosh] |
PostgreSQL's Row Level Security sounds like a clean way to enforce access control at the database layer, but the foot-guns, pooling incompatibilities, and performance traps often make it more trouble than it's worth. →
Simeon Griggs [@simeonGriggs] |
There are many ways to slice a Postgres database for multi-tenant applications. Let's look at the three most common approaches and the trade-offs. →
Simeon Griggs [@simeonGriggs] |
Dead tuples from high-churn job queues can silently degrade your Postgres database when vacuum falls behind—especially alongside competing workloads. Traffic Control keeps cleanup on track. →
Not all traffic is created equal.When a database is overwhelmed, you want the important queries to keep executing, even if that means shedding lower-priority work.This is a much better outcome than the alternative: a total database outage. →
Simeon Griggs [@simeonGriggs] |
A high memory percentage in PlanetScale Postgres is not necessarily a problem. Let's compare how memory and CPU usage are different, how not all memory usage is created equal, and which signals actually require attention. →
Introducing query tagging improvements in Postgres Query Insights →
Learn how Traffic Control enforces real-time limits on Postgres queries. →
Enforce real-time limits on your Postgres query traffic to protect your database from runaway queries and unexpected load spikes. →
PgBouncer is the perfect pairing for Postgres's biggest weakness: connection management. Tuning it just right is important to make this work well, and here we cover everything you need to know →
Nick Van Wiggeren [@NickVanWig] |
Stream real time video and audio through PostgreSQL on PlanetScale. →
Simeon Griggs [@simeonGriggs] |
Build a real-time application with PlanetScale and the Cloudflare global network. Infrastructure choices you won't need to migrate away from once you hit scale. →
What are database transactions and how do SQL databases isolate one transaction from another? →
Postgres 18 is now available on PlanetScale →
Using MotherDuck with PlanetScale →
We've lowered the entry price for using PlanetScale Metal to $50 and added more flexibility in storage-to-compute ratios. →
Introducing AI-powered index suggestions for PostgreSQL →
You can now create single node Postgres databases on PlanetScale starting at just $5. →
Introducing the $5 PlanetScale plan. →
Postgres 18 brings a significant improvement to read performance via async I/O and I/O worker threads. Here we compare its performance to Postgres 17. →