PlanetScale Changelog

The PlanetScale Terraform provider v1.5.0 adds the planetscale_postgres_bouncer resource for managing dedicated PgBouncers, including size, target, replica count, and parameter overrides, with drift detection. Data sources for reading existing bouncers are also available.

pscale role list and pscale password list now accept --name (substring match) and --status (active, renewable, expired) filters.

Schema changes now automatically dismiss deploy request approvals, with planetscale-bot commenting on the changes. Approved deploy requests in the queue are removed and must be re-queued.

New i8ge instance class for Postgres Metal databases offers locally-attached NVMe drives from 1.25 TB on M-160 to 60 TB on M-7680, available in eight AWS regions.

PlanetScale launched a public and free Migration Assessment Tool that accepts reports from the PlanetScale Discovery Tool and provides compatibility blockers, complexity, and recommended next steps for Postgres migrations. The assessment runs client-side and does not send the report to PlanetScale.

Query Insights data is now available through the public PlanetScale API with endpoints for query statistics, errors, anomalies, tags, and traffic budgets. Use a service token with read_database permission to access these endpoints.

You can now configure Vitess read-only region cluster sizes and replicas per keyspace from the Clusters page in the dashboard.

The pscale CLI now includes a pscale sql command to run single queries against database branches with read-only defaults and destructive-statement blocking, a pscale agent-guide command providing machine-readable bootstrap for agents, and structured JSON-format auth onboarding via pscale auth check and pscale auth login so agents can detect and recover from credential or org setup issues.

Postgres roles can now be created with the REPLICATION attribute through the PlanetScale API, dashboard, CLI, and Terraform provider.

The Connect button for Postgres databases now displays existing active roles and allows creating new ones directly, instead of requiring a visit to the Roles page.

You can now download Query Insights query pattern reports from the pscale CLI using pscale branch query-patterns download <database> <branch> --org <organization>, which creates a report, waits for completion, and saves the CSV locally. The --output flag lets you specify the file path.

Query Insights now displays how queries use vindexes on sharded Vitess databases, showing the percentage of traffic that used relevant vindexes and a graph of vindex usage over time, making it easier to spot queries not taking advantage of indexes and measure the impact of index changes on performance.

Query Insights now supports tag-based filtering and navigation for Vitess databases using built-in query metadata or SQLCommenter tags to identify applications, routes, jobs, and other workloads. Filter queries with tag🔑value syntax, explore tag breakdowns in the Tags view, and see tags attached to individual query executions.

VTTablet and MySQL settings can now be configured directly from the Clusters page in the dashboard and through the API.

The PlanetScale Terraform provider v1.3.0 adds planetscale_postgres_redacted_branch_role, a Postgres resource that does not store the plaintext password in Terraform state, allowing password management via your own secret manager.

The planetscale_execute_read_query tool now accepts an optional use_replica parameter (default true) for routing to replicas, and the server warns when Postgres RLS policies may be filtering results returned by read queries.

The Postgres web console now reassigns tables created during a console session to the postgres role shortly after the session ends, rather than leaving them owned by the ephemeral connection role for up to 24 hours.

Postgres branches hosting multiple logical databases can now switch databases from the web console header, or via \connect and \c at the console prompt.

Weekly database reports for Postgres now include egress from the past week, making it easier to track outbound data transfer alongside query performance, schema recommendations, and other usage metrics.