Getting Started
Make sure to first set up your PlanetScale developer environment. Once you’ve installed thepscale CLI, you can interact with PlanetScale and manage your databases straight from the command line.
The branch command
This command allows you to create, delete, diff, and manage branches.
Usage:
Available sub-commands
Service token automation: branch
Legend: ✅ supported · 🚫 unavailable · 👤 interactive login only. All sub-commands require --org or PLANETSCALE_ORG.
* Flag is required
Sub-command flag descriptions
Some of the sub-commands have additional flags unique to the sub-command. This section covers what each of those does. See the above table for which context.The
--region flag can not be used with --restore when creating a branch. Branch backups will be restored to their original region.Available flags
Global flags
Examples
The connections sub-command
Command:
--keyspace and --shard to target a tablet, or run interactively to select them. See
the connections reference, Inspect live Postgres connections,
and Inspect live Vitess connections for the full workflow.
The query-patterns sub-command
Command:
download command creates
a new report, waits for it to finish generating, and downloads the CSV file. See the
query-patterns reference for the full workflow.
The update sub-command
Command:
The extensions sub-command
Command:
CREATE EXTENSION. Preload libraries are configured with
pscale branch resize --parameters. See Postgres extensions.
The switchover sub-command
Command:
--candidate, the named replica is promoted; without it, an eligible replica is selected automatically. On a branch without replicas, the single instance is restarted in place instead. See Switchovers for the full workflow.
The list sub-command with --web flag
Command:
<https://app.planetscale.com/org/database/branches>, in browser.
The parameters sub-command
Command:
--namespace to limit the output
to a single namespace such as pgconf, pgbouncer, or patroni.
The resize sub-command
Command:
--cluster-size), the number of replicas (--replicas), and configuration parameters
(--parameters, repeatable) together. With --wait, the command polls until the change request
completes; without it, the command returns immediately and you can follow up with resize status.
Some parameters require a database restart to take effect; the command tells you which ones before
the change is applied.
Command:
queued, pending,
resizing, completed, or canceled) and what it changes.
Command:
The vtgate sub-command
Command:
--vtgate-size,
--vtgate-count, --vtgate-max-count, --vtgate-autoscaling, or
--vtgate-target-cpu-utilization. Development branches cannot be resized. See the
VTGate documentation for size defaults, autoscaling limits, and pricing.
Command:

