Enable auto_explain from the Extensions tab on your Clusters page and configure parameters like auto_explain.log_min_duration to control which slow queries are logged. This extension is available for all PlanetScale Postgres databases.
These options are available in the dashboard and through the API, making it easier to find and manage roles across your Postgres databases.
]]>Organization members who sign in with an email on your verified domain are automatically added to your organization.
]]>If you find yourself regularly needing to force cutover, you can enable the "aggressive cutover" option in your database settings to make this the default behavior for all deploy requests.
]]>planetscale_postgres_branch or planetscale_vitess_branch creates the parent database if it doesn't already exist. Destroying the last branch in a database deletes the database.]]>You can manage which databases you receive reports for in your user settings.
]]>! to exclude matching results — for example, !table:users returns all queries that don't touch the users table, and !indexed:true surfaces unindexed queries.Positive and negative terms can be combined freely: p99:>100 !table:sessions finds slow queries that don't involve the sessions table. Negation applies to the token immediately following !, so quoted phrases work too — !"some text" excludes queries matching that phrase, while "!some text" treats the exclamation mark as a literal character when searching for queries that include it in the normalized SQL.
Read more about filtering queries with Vitess or filtering queries with Postgres.
]]>gcp-europe-west4).For more information about supported regions, see our regions documentation.
]]>For Postgres databases using Amazon Elastic Block Storage (EBS), you can now set storage size during database creation. This is available in the web dashboard, the API, and the CLI.
]]>The endpoint returns details about storage capacity across keyspaces and shards, including how much additional storage is needed and whether the cluster can be upgraded for more space.
This is useful for catching potential storage issues before deploying large schema changes on Vitess databases.
]]>Use this server when you want AI agents to analyze query performance and suggest optimizations but don't need them to run queries directly against your database.
Server URL:
https://mcp.pscale.dev/mcp/planetscale-insights-only
This is ideal for workflows like the self-improving database, where agents review Insights data and open pull requests with performance improvements.
]]>vectorscale extension.vectorscale is a PostgreSQL extension for high-performance approximate nearest neighbor (ANN) search on vector embeddings.
You can enable vectorscale from the Extensions tab on your Clusters page.
Read more about Traffic Control budgets and warning thresholds in the documentation.
]]>pscale traffic-control command.]]>This option is available across the PlanetScale app, CLI, and API:
pscale branch delete <DATABASE_NAME> <BRANCH_NAME> --delete-descendants.DELETE /v1/organizations/{organization}/databases/{database}/branches/{branch}?delete_descendants=true.Without this option, branch deletion behavior is unchanged.
Read more:
]]>/v1/organizations/{organization}/databases/{database}/maintenance-schedules — List maintenance schedules for a database (GET)/v1/organizations/{organization}/databases/{database}/maintenance-schedules/{id} — Get details about a specific maintenance schedule (GET)/v1/organizations/{organization}/databases/{database}/maintenance-schedules/{id}/windows — List maintenance windows for a schedule (GET)These endpoints are available for Vitess Enterprise customers. To use them with a service token, grant your token read_database permission.
To avoid noise during repeated OOMs, you receive at most one email per database branch per day.
Out of memory (OOM) on Postgres — what happens during an OOM, how to interpret memory metrics, and how to reduce the chance of another one.
]]>You can spin up a fully managed MySQL or Postgres database in seconds, pay for it, and sync your database credentials to your .env file without ever entering the dashboard.
Learn more in the announcement blog.
]]>Traffic Control uses budgets to cap resource usage for specific slices of your workload. Each budget can limit server share (CPU percentage), burst capacity, per-query execution time, and query concurrency. You can target traffic using rules that match on query pattern, application name, Postgres user, or custom sqlcommenter tags.
Budgets run in warn mode to observe what would be throttled, or enforce mode to actively block queries that exceed limits.
Common use cases include incident response, priority-based traffic shaping, protecting user traffic from AI agent workloads, and safe deployments.
]]>The PlanetScale Discovery Tool analyzes your database configuration, schema structure, performance characteristics, security settings, and cloud resources to create a detailed JSON report. Use the report to get tailored migration guidance from PlanetScale.
The Discovery Tool runs entirely on your infrastructure and supports all major cloud providers including AWS RDS/Aurora, Google Cloud SQL/AlloyDB, Supabase, and Heroku Postgres.
]]>This is especially helpful when you're actively working across several databases and need to quickly jump between them.
]]>v0 provider with first-class support for both Vitess and Postgres databases.The v1 provider includes four resources:
planetscale_vitess_branchplanetscale_vitess_branch_passwordplanetscale_postgres_branchplanetscale_postgres_branch_roleAlong with data sources for reading existing databases, branches, roles, and passwords.
v1 is not backwards compatible with v0. If you're currently using the v0 provider, pin your version to ~> 0.6.1 before migrating. The v0 provider will not receive further updates.
gcp-us-east1).For more information about supported regions, see our regions documentation.
]]>Learn more about Postgres pricing or get started with private connections.
]]>branch.out_of_memory, for Postgres databases. This webhook triggers when a Postgres database experiences an out of memory (OOM) event and has to restart.OOM events are serious, they cause your database to restart, drop all active connections, and roll back any in-progress transactions. By subscribing to this webhook, you can be immediately notified when an OOM event occurs and take action to investigate and resolve the issue.
branch.out_of_memory webhooks will send at most once every 30 minutes for databases that are experiencing continuous OOM events.
log_line_prefix parameter for your Postgres databases. This setting controls the prefix format for each PostgreSQL log line, allowing you to include useful metadata like database name (%d), user name (%u), process ID (%p), and timestamp (%m) in your logs.By default, PlanetScale Postgres uses %m [%p] as the log line prefix, which includes the timestamp and process ID. If you need additional context in your logs — for example, to identify which database or user generated a log entry — you can now adjust this through the Parameters tab on your database's Clusters page.
The system always prepends [POSTGRES] to your configured prefix.
This role is designed for team members who need to:
To assign the Analyst role, navigate to your organization's Settings → Members page and update the member's role.
]]>
These columns are helpful for debugging issues related to unusually large response sizes and identifying the most significant contributors to network egress traffic.
]]>paid and overdue status fields, allowing you to monitor invoice payment statuses programmatically.paid — Boolean indicating whether the invoice has been paidoverdue — Boolean indicating whether the invoice is past due and unpaidThese fields are available on both the list and get invoice endpoints:
]]>planetscale_list_schema_recommendations.This tool allows AI agents and MCP-compatible clients like Cursor, Claude, and VS Code to retrieve schema recommendations for your PlanetScale databases. Schema recommendations are automatic suggestions to improve database performance, reduce memory and storage, and optimize your schema based on production database traffic.
With this tool, you can ask your AI assistant to:
We recommend using this tool in the context of the same codebase. Each is a suggestion based on production data and we recommend understanding the pros and cons of each change before implementing. Learn more here.
The tool works with both Vitess and Postgres databases and respects your configured OAuth scopes and permissions.
]]>/v1/organizations/{organization}/databases/{database}/schema-recommendations — List schema recommendations for a database (GET)/v1/organizations/{organization}/databases/{database}/schema-recommendations/{number} — Get details about a specific schema recommendation (GET)/v1/organizations/{organization}/databases/{database}/schema-recommendations/{number}/dismiss — Dismiss a schema recommendation (POST)These endpoints work with both Vitess and Postgres databases. To use them with a service token, grant your token read_database permission. Grant write_database to dismiss recommendations.
You can also use the pscale CLI to access these endpoints:
pscale api organizations/{org-name}/databases/{database-name}/schema-recommendations | jq
]]>pscale database dump command. The new --columns flag lets you specify which columns to include for each table, giving you more control over your database exports.This is useful when you need a partial export or want to exclude sensitive data from your dumps.
# Export only specific columns from multiple tables pscale database dump my-database main --columns 'users:id,name' --columns 'orders:id,total'
The format is table:column1,column2, and you can specify the flag multiple times for different tables. The schema dump will include the complete table schema, but the data files will only contain the specified columns.
This feature is available for Vitess databases only.
]]>Key features:
Available tools:
Use cases include optimizing schemas, debugging slow queries with production context, and querying data using natural language.
]]>OOM events are serious, they cause your database to restart, drop all active connections, and roll back any in-progress transactions. If you see an OOM annotation on your graphs, you should investigate immediately. Common causes include too many connections, memory-intensive queries, or a cluster that needs to be resized.
These annotations make it easier to correlate OOM events with specific query patterns or traffic spikes, helping you identify the root cause.
]]>With log insights enabled, you can:
To use this feature, you'll need to configure the pganalyze collector with a PlanetScale service token.
]]>/v1/organizations/{organization}/teams/{team}/members — List all members in a team (GET)/v1/organizations/{organization}/teams/{team}/members — Add a member to a team (POST)/v1/organizations/{organization}/teams/{team}/members/{id} — Get details about a specific team member (GET)/v1/organizations/{organization}/teams/{team}/members/{id} — Remove a member from a team (DELETE)To use these endpoints with a service token, you'll need the read_organization permission for read operations and write_teams for adding or removing members.
pg_strict blocks dangerous queries before they run. It prevents common mistakes like UPDATE or DELETE statements without WHERE clauses that would affect every row in a table.
The extension is configured per-role, so different users can have different settings. Each setting supports three modes: off, warn, or on. For intentional bulk operations, you can temporarily override the setting within a transaction using SET LOCAL.
This feature is available in the dashboard, API, and CLI.
When creating a service token in the PlanetScale dashboard, you can optionally set an expiration date. The token will stop working once the expiration date is reached.
When creating a service token via the API, you can now include a ttl parameter (in seconds):
curl --request POST \
--url 'https://api.planetscale.com/v1/organizations/{organization}/service-tokens' \
--header 'Authorization: <SERVICE_TOKEN_ID>:<SERVICE_TOKEN>' \
--header 'Content-Type: application/json' \
--data '{"name": "My Token", "ttl": 3600}'
The response now includes an expires_at field showing when the token will expire.
When creating a service token through the pscale CLI, use the --ttl flag to specify the expiration time in seconds:
pscale service-token create --name "My Token" --ttl 3600
The output now displays the expiration time for tokens created with a TTL. You can also see expiration times when listing service tokens with pscale service-token list.
You can now configure your database storage with:
These higher limits give you more flexibility to scale your database storage and performance as your workload grows.
See Cluster Storage for more information on configuring storage settings.
]]>PATCH /v1/organizations/{organization}/databases/{database}/branches/{branch} — Update a branch nameRead the API documentation for details.
]]>To view connection strings, navigate to your database's Settings tab, then go to either the Passwords section (for Vitess) or Roles section (for Postgres), select the role or password, and click "View connection strings".
If a password has been lost, you'll need to create a new password or role to get the full connection string. For Postgres roles, you can also reset credentials to get access to a new password.
Read more about connecting to Vitess | Read more about Postgres roles
]]>wal2json is a logical decoding output plugin that produces JSON format change data capture (CDC) output. This extension enables streaming database changes in a structured JSON format, making it ideal for:
The extension uses PostgreSQL's logical decoding feature to capture row-level changes (INSERT, UPDATE, DELETE) and outputs them as JSON objects, providing a flexible and widely-compatible format for downstream consumers.
]]>planetscale_access label. The label value public indicates public internet traffic, while private indicates traffic over private connections options such as AWS PrivateLink or GCP Private Service Connect.The new label is available in the following metrics:
planetscale_edge_postgres_bytes_sent_totalplanetscale_edge_postgres_bytes_received_totalThese labels help you differentiate between public and private traffic in your monitoring. Example use cases include:
The new import workflow takes your source database connection info, runs compatibility checks, and then monitors every phase of the migration with real-time progress, replication metrics, and traffic switching controls. You can optionally verify data before switching read and write traffic to PlanetScale. Provider-specific guides are available for Aurora, RDS, Azure Database for MySQL, Google Cloud SQL, DigitalOcean, MariaDB, and more.
Learn more in the Vitess database imports documentation.
]]>import { neon, neonConfig } from '@neondatabase/serverless'
neonConfig.fetchEndpoint = (host) => `https://${host}/sql`
const sql = neon(process.env.DATABASE_URL!)
const posts = await sql`SELECT * FROM posts WHERE id = ${postId}`
]]>Note: We don't currently offer an automated in-place upgrade from PostgreSQL 17 to 18. To upgrade, create a new PostgreSQL 18 database and perform an online migration from your existing PlanetScale PostgreSQL 17 database using our import guides.
Read our benchmarks comparing PostgreSQL 17 vs 18 to learn more about performance improvements and what to expect.
For details about the PostgreSQL 18 release, see the official PostgreSQL 18 documentation.
Get started with Postgres to create a database on PostgreSQL 18 today.
]]>pg_duckdb extension for PlanetScale Postgres databases, along with native integration with MotherDuck.pg_duckdb brings DuckDB's columnar analytics engine into Postgres so you can run OLAP queries alongside your OLTP workloads, create DuckDB-backed temporary tables, and query external data sources like Parquet and Iceberg.
When combined with MotherDuck, you can offload heavy analytics queries from your PlanetScale Postgres database to MotherDuck's cloud warehouse while still querying from within Postgres.
]]>M-10, M-20, M-40, and M-80. The M-10 starts as low as $50 per month, making the performance of locally-attached NVMe drives accessible to a wide audience. These also come with more storage configuration options, giving you greater control over your storage-to-compute ratio.
Learn more in the announcement blog and try creating one today.
]]>We'll soon be releasing a new v1 Terraform provider with support for Vitess and Postgres databases.
This will be a complete rewrite of the existing v0 provider and will not be backwards compatible with v0.
If you're currently using the v0 Terraform provider, we recommend pinning your provider version to avoid any breaking changes when the new v1 is released.
]]>
Organizing columns into groups ensures Insights stays easy to navigate as we add more data. Choose from one of the preset groups or create your own view with the "Custom" preset.
]]>The new CLI commands include:
pscale webhook list — List all webhooks in a databasepscale webhook create — Create a new webhook with specific events and URLpscale webhook show — Show details for a specific webhookpscale webhook update — Update webhook settings like enabling/disablingpscale webhook test — Send a test event to verify your webhook is workingpscale webhook delete — Delete a webhookThese commands make it easier to manage webhooks as part of your development workflow or CI/CD pipelines.
]]>Single node databases come with a single primary and no replicas, making them a cost-effective option for development or production workloads that don't require high availability.
To create a single node database, use the --replicas flag with the database create command:
pscale database create <database-name> --engine postgresql --replicas 0]]>
/v1/organizations/{organization}/service-tokens — List all service tokens in your organization (GET)/v1/organizations/{organization}/service-tokens/{id} — Get details about a specific service token (GET)/v1/organizations/{organization}/service-tokens — Create a new service token (POST)/v1/organizations/{organization}/service-tokens/{id} — Delete a service token (DELETE)To use these endpoints with a service token, you'll need the read_service_tokens permission for read operations, write_service_tokens for creating, and delete_service_tokens for deletions.
pscale CLI, making it easier to identify and manage multiple tokens.When you create a service token, you can optionally include a name using the --name flag:
pscale service-token create --name "My Token"
When you list your service tokens with pscale service-token list, you'll now see both the token IDs and their names, making it much easier to find the token you're looking for.
Previously, we used different parameter names for the same thing, such as organization, organization_name, and name all referring to the organization. Now we consistently use organization everywhere. Same goes for database and branch names.
Here's an example of what changed:
- /organizations/{name}/cluster-size-skus
+ /organizations/{organization}/cluster-size-skus
- /organizations/{organization}/databases/{database_name}/cidrs
+ /organizations/{organization}/databases/{database}/cidrs
- /organizations/{name}/regions:
+ /organizations/{organization}/databases:
This won't affect how you use the API, but if you're auto-generating API clients from the spec, you'll get cleaner, more consistent code.
Check out the OpenAPI spec to download the latest version.
]]>
Indexes are crucial for relational database performance. These recommendations help ensure your queries are executing optimally.
Learn more in our in-depth blog and the documentation.
]]>
In the dashboard, you'll find Reset credentials and Reassign objects options on the Role management page. Reset credentials generates a new password for an existing role. Reassign objects transfers ownership of database objects from one role to another.
We've also added two new CLI commands to manage roles in Postgres databases:
pscale role reset --org <org> <database> <branch> <role-id> — Resets the password for a role after prompting for confirmation. Returns the role object with the new password.pscale role reassign --org <org> <database> <branch> <donor> --successor <recipient> — Assigns all objects owned by the donor role to the recipient role.Read the roles documentation for more details on managing Postgres roles.
]]>When you need to transfer ownership of database objects from one role to another, you can now do it via the API:
/v1/organizations/{organization}/databases/{database}/branches/{branch}/roles/{id}/reassign — Reassign all objects owned by one role to another roleNeed to reset a role's password? There's now an endpoint for that:
/v1/organizations/{organization}/databases/{database}/branches/{branch}/roles/{id}/reset — Reset a role's passwordThis generates a new password for the role, which you'll get back in the response.
Read the roles API documentation for more details on managing Postgres roles.
]]>When creating or resizing a Postgres database, you have the option to choose between two types of production databases:
Single-node databases do not come with replicas for high availability, but you can easily switch from non-HA mode to HA mode with just a couple clicks on your Clusters page.
This release also includes our new PS-5 database size and lower prices for PS-DEV Postgres development branches.
Learn more about single-node databases in the announcement blog and in the documentation.
]]>You can now manage organization teams through the API. Create teams, add members, and control database access:
/v1/organizations/{organization}/teams — List and create teams/v1/organizations/{organization}/teams/{slug} — Get, update, or delete a specific teamYou'll need the read_organization permission for listing and viewing teams, and write_organization permission to create, update, or delete them.
Want to know what cluster sizes are available for your organization? The new cluster sizes endpoint returns all available options, optionally with pricing rates:
/v1/organizations/{name}/cluster-size-skus — List available cluster sizes for Vitess or PostgresRead the cluster sizes API docs
You can now manage dedicated PgBouncers and resize them via the API:
Dedicated PgBouncer management:
/v1/organizations/{organization}/databases/{database}/branches/{branch}/bouncers — List and create bouncers/v1/organizations/{organization}/databases/{database}/branches/{branch}/bouncers/{name} — Get or delete a specific bouncerResize operations:
/v1/organizations/{organization}/databases/{database}/branches/{branch}/bouncer-resizes — List all bouncer resize requests for a branch/v1/organizations/{organization}/databases/{database}/branches/{branch}/bouncers/{name}/resizes — List resize requests for a specific bouncer/v1/organizations/{organization}/databases/{database}/branches/{branch}/bouncers/{name}/resizes/{id} — Update or cancel a resize requesttable_keyspace: search term can be used to view and search for queries that reference tables contained within a particular keyspace.table_schema: search term can be used to view and search for queries that reference tables contained within a particular database.schema.
More details about these columns and search terms can be found in the Query Insights for Vitess and Query Insights for Postgres documentation.
]]>/v1/organizations/:name/members — List all members in your organization/v1/organizations/:name/members/:id — Get details about a specific member/v1/organizations/:name/members/:id — Update a member's role (PATCH)/v1/organizations/:name/members/:id — Remove a member from the organization (DELETE)To use these endpoints with a service token, you'll need the read_organization permission for read operations and write_organization permission for updates and deletions.
This can be disabled on a per-database basis from the "Storage" tab on your database's Clusters page by either selecting "Automatically scale disk size up only" or disabling autoscaling entirely.
Read more about autoscaling.
]]>These endpoints let you list, create, update, and delete IP restriction entries. You can optionally scope restrictions to specific schemas or roles, giving you fine-grained control over database access.
Read the API documentation to get started.
Note: For Vitess databases, you can manage IP restrictions using the existing branch password endpoints by specifying the cidrs parameter when creating or updating passwords.
We've just released the ability to provision dedicated PgBouncers for your Postgres replicas. Dedicated PgBouncers run on nodes separate from Postgres.
This allows you to have a connection pool that will evenly distribute connections across your available replicas, making it simple to scale out read-only traffic by using your two included replicas or even scaling out more by adding additional replicas to your Postgres cluster.
]]>This extension will become available to all PlanetScale Postgres databases at their next maintenance window and can be enabled through the Extensions tab on your Clusters page.
]]>Thank you to Michael Timbs for the idea.
]]>Read-only mode preserves cluster functionality while preventing write operations that could lead to instability. Your cluster will automatically exit read-only mode once the underlying issue is remediated.
This feature is rolling out to customers this week and will be available to all customers gradually over the course of 2-3 weeks, depending on your maintenance window.
]]>For Vitess databases with one or more sharded keyspaces, you can now use the Tablet calls per query column to view the average number of tablets that are used during query execution for each query pattern. This data can help you identify queries that require distributed execution across multiple tablets, and monitor how this quantity is changing over time.
More details about these and other columns can be found in the Query Insights for Vitess documentation.
]]>--output-format flag with the pscale database dump command.The new flag supports three output formats:
sql (default) - MySQL INSERT statements for direct importjson - JSONL format with one JSON object per linecsv - CSV format with headers for easy analysis# Export as JSON pscale database dump my-database main --output-format=json # Export as CSV pscale database dump my-database main --output-format=csv # Export as SQL (default) pscale database dump my-database main --output-format=sql
This feature is available for Vitess databases only.
Thanks to @ivov for contributing this feature!
]]>These columns are represented in units of "blocks": data chunks that are stored in the PostgreSQL shared buffer cache, and are the same values that are included in the buffer usage information returned by the EXPLAIN ANALYZE statement.
These new columns are:
More details about these and other columns can be found in the Query Insights for PostgreSQL documentation.
]]>
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.
This feature is currently available for Vitess databases only.
]]>
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.
This feature is available for all Postgres databases.
]]>These columns are helpful for finding unexpectedly large query responses and the most significant contributors to network egress traffic. To enable these columns visit the Insights dashboard and check "Bytes returned" and "Bytes returned per query" under "View options"
gcp-europe-west1).For more information about supported regions, see our regions documentation.
]]>branch.start_maintenance webhook is now available for Vitess databases. This webhook is available for enterprise customers with maintenance windows configured.When you subscribe to this webhook, you'll get a notification right before maintenance starts for your production branch. During maintenance, Vitess and security upgrades are rolled out, and any queued cluster configuration changes are applied.
]]>
branch.start_maintenance. This webhook is available for Postgres databases only.By subscribing to this webhook, you'll get a notification right before maintenance for your production branch is about to start. Your database cluster might restart, causing connections to be temporarily disconnected.
]]>Note: To see the I/O columns, you'll need to first enable the track_io_timing parameter on your database's Clusters page.
You can get started from either the Cloudflare dashboard or right from your PlanetScale database's Connect page - just select "Cloudflare" from the connection options and follow the setup instructions.
]]>Check out the blog post to learn more.
]]>Schema recommendations are automatic suggestions to improve database performance, reduce memory and disk usage, and improve your schema.
PostgreSQL schema recommendations automatically suggest fixes to the following conditions:
During maintenance windows, your database will restart, causing connections to temporarily disconnect.
]]>autoinc - Functions for autoincrementing fields, providing automatic sequence-based field incrementing functionality.
bloom - Bloom filter index access method that provides space-efficient probabilistic data structure for fast membership testing.
dict_xsyn - Text search dictionary for extended synonym processing, enhancing full-text search capabilities with advanced synonym handling.
earthdistance - Calculate great circle distances on the surface of the Earth, perfect for geospatial applications requiring distance calculations.
insert_username - Functions for tracking who changed a table, automatically recording user information for audit trails.
intagg - Integer aggregator and enumerator functions (note: this extension is deprecated but available for legacy compatibility).
moddatetime - Functions for tracking last modification time, automatically updating timestamp fields when records are modified.
pgrowlocks - Show row-level locking information for debugging and monitoring database lock contention.
pgstattuple - Obtain tuple-level statistics to analyze table storage efficiency and bloat.
postgres_fdw - Foreign data wrapper for remote PostgreSQL servers, enabling federated queries across multiple PostgreSQL instances.
All extensions are now available for PlanetScale Postgres databases and can be enabled through the Extensions tab on your Clusters page.
]]>Where previously our scoping only included Managed deployments on AWS, PCI compliance is now possible with any PlanetScale Managed deployment, regardless of whether the data plane is deployed in your own AWS or GCP account. Be sure to review our updated Shared Responsibility Matrix to understand the controls you are required to maintain for your specific deployment.
If you are interested in running PCI-scoped workloads on PlanetScale Managed, contact us for details. Existing enterprise customers may request the latest copies of our PCI reporting by visiting our Trust Center.
]]>For more information about supported regions, click the Regions dropdown on the pricing page.
]]>To enable AWS PrivateLink for your database, see the AWS PrivateLink documentation.
]]>
aws-ca-central-1.]]>No additional configuration is required. Simply create your event triggers using standard PostgreSQL syntax:
CREATE EVENT TRIGGER abort_ddl ON ddl_command_start EXECUTE FUNCTION abort_any_command();]]>
pg_squeeze runs as a background worker that periodically checks registered tables for bloat and performs automatic cleanup without blocking read/write operations. To use it, register tables by inserting records into the squeeze.tables table, then start the background worker with squeeze.start_worker(). Alternatively, you can process a table immediately with SELECT squeeze.squeeze_table('schema', 'table_name').
This extension is now available for all PlanetScale Postgres databases and can be enabled through the Extensions tab on your Clusters page.
]]>Metal instances are designed for workloads that require high, sequential read and write access to very large data sets on local storage. They are optimized to deliver tens of thousands of low-latency, random I/O operations per second (IOPS) to applications.
Schedule SQL commands to run at specific times using familiar cron syntax, directly within your PostgreSQL database.
Automate table partition maintenance with this background worker extension that works alongside pg_partman. It automatically handles partition creation, deletion, and maintenance without manual intervention.
Both extensions are now available for all PlanetScale Postgres databases and can be enabled through the Extensions tab on your Clusters page.
]]>pscale shell command now works with Postgres databases! Postgres connections use psql to connect directly to your database with no local proxy required.New features include:
--replica flag to connect to read-only replicas--role flag supporting reader, writer, readwriter, and admin roles:5432 for optimal performance (bypassing the pooler)This enhancement makes it even easier to interact with your Postgres databases directly from the command line.
Read more in our CLI documentation.
]]>Our new Postgres migration guides provide detailed instructions for three migration approaches:
Each guide includes setup instructions, best practices, and troubleshooting tips.
We've also released migration scripts on GitHub to automate common migration scenarios:
The scripts handle connection management, sequence handling, and provide monitoring capabilities throughout the migration process.
]]>pscale role commands to the PlanetScale CLI, bringing Postgres role management capabilities directly to your command line.pscale role create <database> <branch> <name> - Create a new role for a Postgres database branchpscale role delete <database> <branch> <role-id> - Delete a rolepscale role get <database> <branch> <role-id> - Retrieve information about a specific rolepscale role list <database> <branch> - List all roles for a Postgres database branchpscale role renew <database> <branch> <role-id> - Renew a role's expirationpscale role reset-default <database> <branch> - Reset the credentials for the default postgres rolepscale role update <database> <branch> <role-id> - Update a role's nameRead more in our Postgres roles documentation.
]]>
As before, you can also create roles via CREATE ROLE commands directly on your Postgres server. Read more:
On the "Storage" tab of your database's Clusters page there are now options to configure the provisioned input/output operations per second (IOPS) and bandwidth.
The maximum amount of IOPS and bandwidth that can be provisioned is based on the cluster size of your database and minimum disk size.
See Cluster Storage for more information on configuring network-attached storage on Postgres clusters.
]]>To access these reports as well as all of our other compliance documentation, please visit our Trust Center.
]]>If you are using the VStreamer functionality, you will now receive both the total events successfully streamed and any errors thay may have occured during the process.
]]>From this tab, you can now control your disk size and autoscaling settings.
Network-attached storage is limited to changing sizes every 6 hours. If you are importing a large amount of data, we recommend scaling your drive up before starting the import.
]]>Learn more in our announcement blog.
]]>For sharded databases, the storage estimation is broken down per shard, giving you detailed visibility into the storage requirements for each individual shard.
If there is not enough available disk space to complete the deploy request, the deployment will be prevented from starting. In this case, you'll need to upgrade your cluster to a larger storage tier before the deploy request can run.
Learn more about artifact tables and storage considerations in our documentation.
]]>/v1/organizations/{organization}/databases/{database}/branches/{branch}/keyspaces/{keyspace}/vschemaNew write_production_branch_vschema and write_branch_vschema service token scopes have also been added. You may grant these new scopes to your service token by visiting your organization service token settings page.
When enabled, this setting forces schema migration cutover operations to complete immediately by killing any queries or transactions that are blocking the operation. This is useful when you receive "Migration delayed due to long-running transactions" notices or when your application has slow queries that prevent migrations from completing.
Important: This setting applies to all future deploy requests once enabled, and killed queries will need to be retried by your application.
For more information, see the Aggressive cutover documentation.
]]>database.access_request. It will trigger when a member of PlanetScale staff opens a request for temporary access to your organization for support purposes.This webhook can be useful when wired up to a pager or alerting system.
]]>/v1/organizations/:name/databases/:database/webhooks/v1/organizations/:name/databases/:database/webhooks/:id/v1/organizations/:name/databases/:database/webhooks/:id/testTo use with a service token, grant your token write_database and read_database permission.
keyspace.storage. With this new event you can receive a webhook whenever your PlanetScale Metal database crosses a storage threshold (60%, 75%, 85%, 90%, 95%).Example payload:
{
"timestamp": 1745526125,
"event": "keyspace.storage",
"organization": "example-org",
"database": "example",
"resource": {
"branch_name": "main",
"keyspace_name": "example",
"storage_percentage": 44,
"shards": [
{
"shard": "x-x",
"bytes_used": 208470605824,
"bytes_total_capacity": 472424366080,
"bytes_available": 263953760256,
"storage_percentage": 44.1
}
]
}
}
]]>The full list of edge metrics is available in the metrics reference documentation.
Learn more about exporting metrics in our documentation.
]]>Additionally, we've added the ability to adjust or disable the refresh interval for the page.
Note: The PlanetScale MCP server is now authenticated and externally hosted for even better integration with your projects. See the MCP documentation for setup instructions.
We have shipped Model Context Protocol (MCP) support, enabling seamless integration between PlanetScale databases and AI tools. This integration allows tools like Claude or Cursor to directly access read-only database information to answer your questions more intelligently.
We have two new CLI Commands you can use to get up and running
pscale mcp install --target <claude|cursor|zed> # Installs the PlanetScale MCP server config for your tool pscale mcp server # Enables your AI tool to perform read-only database interactions
Using this functionality allows you to interact with your PlanetScale organizations and databases right from your AI tooling. You can ask questions like "How many users do I have in North Carolina?" or "How many rows are in my messages table?" Claude, Cursor, Zed, or other tools will then be able to access read-only info from your PlanetScale account to give bespoke answers. You can get started using Claude, Cursor, or Zed using the instructions below.
For Claude Desktop:
pscale mcp install --target claudeFor Cursor:
pscale mcp install --target cursorIf you prefer to configure Cursor (or another MCP-compatible tool) manually, add the following to your .cursor/mcp.json in your project or home directory
{
"mcpServers": {
"planetscale": {
"args": [
"mcp",
"server"
],
"command": "pscale"
}
}
}
For Zed:
pscale mcp install --target zedOther tools should accept a configuration similar to the Cursor example above.
]]>You can use workflows to shard tables through unsharded to sharded keyspace workflows, further shard your tables through sharded to sharded keyspace workflows, and migrate tables between keyspaces using unsharded to unsharded keyspace workflows.
To get started, read more about workflows in our docs.
]]>Learn more about how to set it up:
]]>
Replication is configured to maximize safety and data integrity. This default configuration can be relaxed for performance improvements and reduced replication lag.
These settings improve performance during VReplication processes like deploy requests and workflows.
Learn more in our cluster configuration documentation.
]]>AUTO_INCREMENT primary indexes.If you're familiar with Vitess, these options map to the --defer-secondary-keys, --on-ddl, and --global-keyspace parameters to MoveTables.
Learn more in our Workflows documentation and Sharding quickstart.
]]>To get started with vectors, go to the “Branches” page. Click on the branch you want to add vectors to, and click on the small gear icon underneath the “Connect” button. Click the toggle next to “Enable vectors.” Follow the examples in the vectors documentation to create a vector column, add data, and create and query an index.
Read more in the blog post.
]]>
To learn more about VTGates and how to configure them, see the VTGate documentation.
]]>Metal nodes are generally available and ready for production workloads. Several customers, including Block and Intercom, have been running on Metal for months prior to public release.
Learn more about PlanetScale Metal:
]]>VTG-5 to VTG-10VTG-320 and larger)VTG-320 and larger)To learn more about VTGates and how to configure them, see the VTGate documentation.
]]>Adding or removing shards from a sharded keyspace requires some rebalancing, as you may be moving data from one MySQL instance to another. This involves creating a new sharded (target) keyspace with the desired number of shards and transferring all of the data from your current (source) keyspace to the new target. This operation is done with no downtime.
For the full tutorial, see the Sharding a sharded keyspace documentation.
]]>
As of pscale version 0.220.0, you can check keyspace rollout progress with pscale keyspace rollout-status <database> <branch> <keyspace>.
The show keyspace rollout endpoint is now available.
For more information, see the PlanetScale architecture documentation.
]]>
Learn more in the Deploy requests documentation.
]]>The throttle setting is a value between 0 and 95, where 0 means no throttling and 95 is nearly fully throttled, drastically slowing down migrations. The throttle setting can be configured at the database level, keyspace level, or per-deploy request.
For more information, see the Throttling deploy requests documentation.
]]>This change brings support for product_quantization and fixed_quantization. You can configure these for your indexes by specifying them in the SECONDARY_ENGINE_ATTRIBUTE when creating your indexes. For example:
CREATE VECTOR INDEX embedding_index ON table_1(embedding)
SECONDARY_ENGINE_ATTRIBUTE='{"type":"spann", "distance":"l2", "product_quantization":{"dimensions":96}}';
CREATE VECTOR INDEX embedding_index ON table_1(embedding)
SECONDARY_ENGINE_ATTRIBUTE='{"type":"spann", "distance":"l2", "fixed_quantization":"bfloat16"}';
Learn more in our vectors documentation.
]]>If you're familiar with Vitess, this workflow is analagous to MoveTables, a critical component to managing your data distribution in Vitess. We are excited to now offer this functionality directly in PlanetScale.
Learn more in our Workflows documentation and Sharding quickstart.
]]>
Query statistics sparklines make it easy to quickly scan your database workload to identify how individual query patterns are changing over time.
]]>From here, you can also modify the VSchema for your keyspaces.
Please be aware of the following limitations:
For more information, please refer to the Cluster configuration documentation.
]]>
When granting access to all databases, the permissions will apply to both current and future databases. Additionally, they cannot be removed individually from any database.
This is now available to organization administrators on the service token permissions page.
]]>We have since deprecated those legacy connection strings, but a small number of databases are still using them.
If you are affected, you will have received daily emails from us informing you about the upcoming brownouts and requirements for updating your connection strings.
As previously communicated, brownouts began on September 3rd, 2024. During these brownout periods, you will be unable to connect to your database.
Brownouts will continue Monday through Friday throughout September. The brownout duration will increase throughout the month leading up to October 1st, 2024, at which point we will completely deprecate legacy connection strings.
On October 1st, 2024, we plan to completely deprecate legacy connection strings and will stop serving connections to databases using them.
If you are affected, you will continue to receive several more emails leading up to this date. It is extremely important that you update your connection strings for your database to remain active.
To update your connection string, go to the PlanetScale dashboard -> your database -> settings -> passwords.
Create a new password and update the hostname, username and password in your application.
We want this process to be simple and painless for everyone. If this causes any difficulties for you, please reach out to our support team.
]]>Enterprise customers may request the latest copies of our PCI documentation by contacting Support or visiting our Trust Portal.
]]>
create_databases, will automatically be granted full permissions to any database that it creates.With this change, you can fully automate creation + management without needing to grant more permissions to your service token.
]]>Your preference will be saved and persist across browser sessions.
max_latency. This column shows the maximum response time of any individual query pattern in the selected time window. Maximum is often a useful metric for spotting extreme outliers that may not show up in p99 (99th percentile). To enable the Max latency column, visit your Insights dashboard, click on the columns menu to the right of the query filter search box, and check "Max latency".
You can also filter query patterns based on max latency by adding max_latency:>x where x is measured in miliseconds.
When using "Set as default branch" you can optionally choose to have the children of the current default branch move over with it.
Permissions:
With these changes, you now have more control over the organization of your branches.
]]>SELECT queries. To see index usage, click on a query from your Insights dashboard, and then click on the new Indexes tab.
This view shows a time series graph of the percent of queries that use each listed index. The vertical bar chart near the bottom shows comprehensive index usage information for the entire period.
You can also search for queries based on index usage:
index:$TABLE.$INDEX_NAME to the insights search barindexed:falseIn addition to index usage, we've also added summary statistics (total time, latencies, etc) to the query details page.
Read the blog post for more information.
]]>
To receive a copy of the report, please contact Support or visit our Trust Portal.
]]>
We've heard your feedback and Insights graphs now show all x-axis time measurements as an absolute time (e.g. 09:31) instead of as a relative time offset (e.g. 3h ago). Absolute time offsets make it easier to correlate Insights data with information from external systems.
]]>
We've increased the resolution for all Insights graphs. Graphs with periods from 12 to 24 hours now show data in 5 minute increments (down from 10 minutes) and periods under 12 hours show data in 1 minute increments (down from 5 minutes). Smaller time buckets result in less smoothing and make it easier to spot temporary fluctuations.
]]>deploy_request.pending_cutover.This event will trigger when a deploy request is ready to apply the schema and is waiting on the user to confirm.
For deploy requests that have "auto_cutover" or "Auto apply" enabled, this webhook will not be sent.
This new event is now available in your webhook settings.
]]>
We just shipped an improvement to deploy requests. Now, you can optionally set your deploy requests to delete the development branch once fully complete.
You can do this by toggling a checkbox while the deploy request is running. This new setting is also available via the CLI and API.
It is disabled by default and must be enabled for each deploy request. The branch will only be deleted if the deployment is successful and the revert period is complete.
As of pscale version 0.205.0, you can create a deploy request with pscale deploy-request create db branch --auto-delete-branch and the setting will be enabled.
The create deploy request endpoint now has auto_delete_branch available. Set this parameter to true to enable the setting.
A small number of databases are still using connection strings from before this change. In the coming weeks we are working on deprecating the usage of these strings and getting everyone upgraded.
We are sending emails to all account admins for databases which are still connecting via legacy strings.
You may also check the hostname for your connection string. If it shows the ID for the database branch, then it is a legacy string.
Examples:
abcdeabc1234.us-east-1.psdb.cloudaws.connect.psdb.cloudTo update your connection string, go to the PlanetScale dashboard -> your database -> settings -> passwords.
Create a new password and update the hostname, username and password in your application.
We will be performing multiple brownout periods starting September 3rd, 2024. During these, connections to your database will stop working.
The purpose of the brownout periods is to help alert anyone who is still unintentionally using a legacy connection string.
After several brownout periods, we will re-evaluate usage again and send final notices to anyone still using a legacy connection string before fully deprecating.
If you are using an old version of the pscale CLI, you may see the following message when trying to use pscale shell or pscale connect.
Your version of pscale is too old and is using a deprecated connection method. Please update your CLI version.
If this impacts you, please update pscale to the latest version.
We want this process to be simple and painless for everyone. If this causes any difficulties for you, please reach out to our support team.
]]>If there is more than one administator, then self-approval is not allowed.
]]>
We have made an update to schema recommendations. Now when closing a recommendation, you can leave an optional comment explaining why the recommendation is being closed.
Comments support Markdown.
]]>database and organization names.{
"timestamp": 1698252879,
"event": "branch.ready",
+ "organization": "my-org",
+ "database": "example_database",
"resource": { ... }
}
]]>/v1/organizations/:name/audit-logA new service token scope read_audit_logs has also been added. You may add this to your service token by visiting your service token settings.
pscale connectpscale shellpscale database dumppscale database restore-dumpPlease update your CLI to version v0.182.0 or later to continue using these commands.
]]>write_database permission.]]>Why make this change? We needed to make room for new features. We were starting to be limited by the space available along the top navigation bar. The new side navigation allows for more space and keeps everything easily discoverable.
]]>planetscale.vtgate.errors metric name within your Datadog widget and notebooks.]]>The organization switcher has been improved as well. It will show all of your pinned databases across all of your organizations.
]]>read_invoices permission.]]>This is helpful in cases where your compliance mandates that your connections do not route through the public Internet, or for customers looking to save costs on their NAT Gateways.
]]>p50:>250 in the insights search box.]]>With replica credentials, it makes it easier to query your database's replicas and read-only regions by creating a password dedicated for replica use. These new credentials will be routed to the nearest read-only region with the lowest latency as new regions are added or removed without any code changes or even needing to reconnect.
]]>The webhook event is branch.anomaly and includes the full database branch information in the payload.
auto-apply setting. If you turn it off, all future deploy requests will default to the setting being off.]]>To enable monthly spend alerts, go to your organization billing page, click "Enable spend alerts", and enter the maximum spend amount. Organization admins will receive an email once monthly spend hits 75% and 100%.
]]>planetscale.primary.cpu_usage and planetscale.primary.memory_usage metric names within your Datadog widgets and notebooks.]]>With schema recommendations, you will automatically receive recommendations to improve database performance, reduce memory and storage, and improve your schema based on production database traffic.
Schema recommendations uses query-level telemetry to generate tailored recommendations in the form of DDL statements that can be applied directly to a database branch and then deployed to production.
]]>On the database’s ”Dashboard” page, you will see a loading spinner that says it is “Enabling foreign key constraints.” Once it no longer shows, you can use foreign key constraints in your PlanetScale database!
For most cases, foreign key constraints should work as expected in PlanetScale. There are a few cases to be aware of that are unsupported or result in less ideal behavior. You can read more in the limitations section of the foreign key constraints documentation.
If you don't have an existing PlanetScale database and have an existing internet-accessible MySQL or MariaDB databases that use foreign key constraints, you can also import it into PlanetScale using our database import tool.
]]>If you are interested in building on top of PlanetScale and allowing your users to authenticate with PlanetScale to gain management access to their organizations and databases, you can create your OAuth application in your PlanetScale organization’s Settings > OAuth applications page.
]]>Read the announcement blog post for more information.
]]>To opt-in an existing database, go to your database’s ”Settings” page and enroll on the ”Beta features” page. See the full documentation for more details about the beta.
]]>The new Anomalies tab in Insights warns you of any anomalies that have occurred in the last 24 hours, with additional information about:
It is available today in private preview to Fivetran users. You can request access to the PlanetScale connector from within Fivetran. See our Fivetran integration documentation for more info.
]]>Initially, all users will be subscribed to weekly reports for the most active database in their organizations. You can unsubscribe directly from the email or in your user settings.
]]>To learn more, check out the blog post.
]]>For more information about Insights, see our Insights documentation.
]]>Find the page in your database’s “Settings” tab > “Passwords” section > select the password you want to see the details for.
]]>For supported regions, see our regions documentation and see our read-only regions documentation to learn more about read-only regions in PlanetScale.
]]>To receive a copy of the report, please contact Support or visit our Trust Portal.
]]>Scaler Pro databases are priced on a combination of resources (CPU and memory) and disk storage. Every database has a ‘cluster size’ encompassing the components that make up a PlanetScale database.
Note: The Scaler Pro plan has since been renamed to the Base plan.
]]>For more information, see our Pulling back the curtain: the new database overview page blog post.
]]>For more information about our supported regions, see our documentation.
]]>gcp-asia-northeast3)For more information about limitations and supported regions, see our GCP documentation.
]]>Read how the PlanetScale Engineering team used this feature to troubleshoot a query in our primary production database.
]]>Historical availability events have been populated and the page is available at https://www.planetscalestatus.com.
]]>Previously, protection from direct DDL was enabled by default on all production branches with no option to disable it. With this change, when you promote a branch to production, you will now see a toggle that asks if you want to enable safe migrations.
Read more about why we introduced safe migrations in our latest blog post, “An update to our workflow: safe migrations”.
]]>gcp-us-east4) and Montréal, Québec, Canada (gcp-northamerica-northeast1).For more information about limitations and supported regions, see our GCP documentation.
]]>The PlanetScale API (beta) opens up new ways to interact with PlanetScale through automation and other developer tools, like CI/CD, infrastructure as code, deployment tools, and application platforms.
In addition to the API, we are also launching OAuth applications in limited beta. OAuth applications alongside the PlanetScale API enable your users to interact with their PlanetScale databases from your application.
]]>Contact us for more information about the PlanetScale Single-tenant offering and how to enter into a BAA with PlanetScale.
Please refer to the Security and compliance documentation for more details about PlanetScale and HIPAA.
]]>For more information about limitations and supported regions, see our GCP documentation.
]]>EXPLAIN statements.To enable complete query collection, an Organization Administrator must opt in on your database settings page.
]]>To learn more, check out our Gated Deployments documentation or the Gated Deployments: Addressing the complexity of schema deployments at scale blog post.
]]>aws-eu-west-2.]]>This Fetch API-compatible driver allows you to use PlanetScale with serverless and edge compute platforms that require HTTP connections, such as Cloudflare Workers, Vercel Edge Functions, and Netlify Edge Functions.
To use this driver, you must opt-in and accept beta terms to access the required PlanetScale connection strings. You can enroll your database by selecting the database in the PlanetScale dashboard, clicking "Settings", "Beta features", and clicking "Enroll" next to "PlanetScale serverless driver for JavaScript".
]]>Teams is available on all plans.
]]>Insights brings a new interactive graphical interface that charts query performance along side your Deploy Requests.
We’ve also added a new section that surfaces all queries run against your database in the last 24 hours. Each query includes metrics such as rows read, rows returned, time per query, and more.
Insights is currently in beta. You can try it out for yourself by clicking the “Insights” tab on your database page in the PlanetScale dashboard.
]]>For this release, we’ve implemented an Airbyte connector as the pipeline between your PlanetScale data and the desired destination.
Connect is currently in beta. You can opt-in on your Organization Settings page under “Beta features”.
]]>Portals is available on our Scaler, Teams, and Enterprise plans and will be billed based on storage and rows read. For more information, check out our Read-only regions documentation.
Portals is currently in beta. You can add a read-only region and try it out on any production branch in your organization.
]]>The new Teams plan includes:
We’ve also made some updates to existing plans. Our free Developer plan is now called Hobby and comes with 5 GB storage, 1 production branch, and 1 development branch.
Our Scaler plan has been updated to include SSO as an add-on option, 10 GB storage, 2 production branches, and 5 development branches.
]]>eu-central-1), Sydney (ap-southeast-2), and São Paulo (sa-east-1).]]>If you create and deploy a deploy request with a schema change that breaks your application, you can instantly revert the deployment with the click of a button. Additionally, you’ll retain any data that was added to your production database during the time between deployment and reverting.
This feature is in limited beta and you must accept beta terms and enroll your database to use it. For more information, see the Revert a schema change section of our Deploy requests documentation.
]]>The free Developer plan remains at 10 GB of storage and 10 million writes, but now includes 1 billion reads.
The Scaler plan remains $29 per month per database with 25 GB of storage and 50 million writes, but now includes 100 billion reads. Additional storage and usage for the Scaler plan will be charged at $2.50 per additional GB, $1 per additional 1 billion rows read, and $1.50 per additional 1 million rows written.
]]>The following criteria is used to determine when a database is eligible to sleep:
Once all criteria is met, the database will enter sleep mode. You can wake a sleeping database at any time from the PlanetScale dashboard.
]]>Check out our latest blog post to learn more about how to import your data.
]]>Database Administrator.The permissions for the Database Administrator role are granted at the database level. With this role, you can give a member of your organization full access to a specific database (or several databases) without making them an Organization Administrator.
For larger organizations, we now offer a customizable, resource-based Enterprise plan that includes features like Single sign-on, unlimited database branches, premium support, and more.
To ensure we can provide the best quality service for our free Developer plan databases, we will be limiting the number of Developer plan databases to one per organization.
]]>main branch will be a development branch by default, allowing you to start making changes to the schema instantaneously, without needing to use deploy requests. When you're done hacking around and ready to make your database production-ready, you can promote your branch to production, which enables high-availability and direct DDL protection (sorry Little Bobby Tables). Additionally, you can promote multiple branches if you so desire, so if you want to have a staging database branch that’s also protected, we can do that for you!Lastly, we’ve introduced the concept of a default branch. Before, main was the default branch and that wasn’t able to be changed. But now, you can select whatever you want as the default branch. One thing to note, the first branch that gets promoted to production will become the default branch.
To set a default organization, head over to your user settings and select your default organization from the drop down.
]]>The PlanetScale web console is an interactive interface for running MySQL queries and DDL (Create, Alter, & Delete) against your PlanetScale database branches.
]]>The Prisma Data Platform provides you with application templates with Prisma data schemas, so you don’t even have to think about a data model to get started. Once set up, you can deploy to Vercel immediately or use the Prisma Data Explorer and Query Builder to explore your PlanetScale database.
]]>Set up automatic migrations with your first deploy request by selecting the framework of your choice. If the framework you’re using isn’t listed, select “Other” and enter the name of the migration tracking table.
Once set up, you’ll never have to worry about keeping the framework’s migration table up to date. It will happen automatically.
]]>Within PlanetScale, you can generate a new password and automatically get client code for many popular frameworks and languages for you to connect your PlanetScale database.
PlanetScale connection strings are built with security as a priority, so you can spend less time worrying if your database connections are secure. This includes strong passwords that are never stored in plain text, GitHub Secret Scanning, and native MySQL authentication support.
]]>We have also added the ability to deploy branches near where you develop. Deploy your production branch near your users and develop on a branch in your region to avoid unnecessary latency.
]]>If you're authenticating via GitHub OAuth or SSO, MFA settings will not be displayed
]]>