Changelog
The latest PlanetScale features and product launches. Get the RSS feed.
Single-node databases are now generally available
Single node Postgres databases are now available to all customers, starting at just $5 per month. Single node databases are a cost-effective option for early-stage projects, testing, development, and proof of concepts. →
New API endpoints for organization teams, cluster sizes, and PgBouncer resizes
We've added several new API endpoints. →
SLA single node excluded
We have removed the upcoming single node sizes as well as development branches from our SLA. For more information, see the PlanetScale Service Level Agreement page. →
Automatically shrink Postgres network-attached storage disks
We've just released automatic disk shrinking for Postgres databases using network-attached storage. When your database is using less than 12.5% of the allocated disk space for more than 72 hours, we will automatically shrink the disk to the next available size.This helps you save money by only paying for the storage you need. →
Organization member API endpoints
We've released new API endpoints for managing organization members. →
Insights - Table keyspace/schema column and search filtering
It is now easier to find queries that reference tables within a particular Vitess keyspace or PostgreSQL schema, regardless of the keyspace that was associated with the database connection that issued the original query. →
Dedicated replica PgBouncers with availability zone affinity
Dedicated replica PgBouncers may now be configured to prefer routing to the Postgres replica servers inside their own availability zone. Applications deployed across several zones can benefit from lower replica query latency in this configuration. →
Dedicated primary PgBouncers
We've just released the ability to provision dedicated PgBouncers for your Postgres primary servers. A dedicated primary PgBouncer provides connection pooling for your primary database, running on nodes separate from the Postgres servers. Connections through dedicated PgBouncers persist through cluster resizes, upgrades, and most failover scenarios, providing improved high availability. →
Postgres IP restriction API endpoints
We've added new API endpoints for managing IP restrictions on Postgres databases. You can now programmatically control which IP addresses or CIDR ranges have access to your databases. →
Dedicated replica PgBouncers
We've just released the ability to provision dedicated PgBouncers for your Postgres replicas. Dedicated PgBouncers run on nodes separate from Postgres. →
Postgres IP restrictions
You can now define which IP addresses can connect to each branch for PlanetScale Postgres databases using IP restrictions. IP restrictions give you more control over which clients can establish connections to your database. →
New Postgres extension: TimescaleDB
We've added TimescaleDB, a time-series database packaged as a PostgreSQL extension that transforms Postgres into a high-performance database for real-time analytics. All features of the Apache 2 Edition are supported. →
Vitess passwords search and filtering
We just shipped an upgrade to the Vitess passwords page. It now includes search and the ability to filter between active and expired passwords. →
Read-only mode
We will now automatically enable read-only mode on Postgres clusters to maintain stability and availability when certain conditions are detected, such as insufficient storage space or extreme replication lag. →
Copy schema recommendations as Markdown
We've added a "Copy page as Markdown" button to all Insights schema recommendations, making it easy to get an LLM-friendly description of your schema recommendation. →
Insights - Vitess tablet calls per query metrics
We've added a new column to Insights for Vitess databases to help you better understand the behavior and performance impact of queries that require communicating with multiple shards (VTTablets) during their execution. →
PostgreSQL Block Usage Metrics
We've added 5 new columns to Insights for PostgreSQL databases to help you better understand the effect of the shared buffer cache on your query performance, enabling you to better tune your server configuration or database sizing for optimal performance. →
Multiple output formats for database dump
You can now export your Vitess database data in multiple formats using the new --output-format flag with the pscale database dump command. →
Replica connections graph
You can now view connection metrics for your database replicas on the metrics page. These graphs help you monitor connection usage across your primary and replica instances, making it easier to identify connection patterns and optimize your database performance. →
Branch page table sorting
You can now sort tables on your branch page by name or size. This makes it easier to find the largest tables in your database. →
Neon serverless driver support for PlanetScale Postgres
PlanetScale now supports connections via the Neon serverless driver using WebSocket connections, making it easier to connect to your PlanetScale Postgres databases in serverless environments like Vercel Functions and AWS Lambda. Note that only the WebSocket mode is supported - the HTTP/fetch mode is not compatible with PlanetScale. →
Insights - PostgreSQL query response size metrics
We've added 2 new columns in Insights to help track the response size of PostgreSQL queries. →
New GCP region: St Ghislain, Belgium
We have added a new GCP region. Now you can deploy Postgres and Vitess databases on GCP in St Ghislain, Belgium (gcp-europe-west1). →
Branch start maintenance webhook now available for Vitess enterprise customers
The branch.start_maintenance webhook is now available for Vitess databases. This webhook is available for enterprise customers with maintenance windows configured. →
Deploy request UI updates
We've just shipped a couple updates to the Vitess deploy requests UI for databases with multiple keyspaces. →