> databases & regions
Provisioning and inspecting the databases themselves: create a MySQL (Vitess) or Postgres database in a region near your app, list what exists, check region and cluster-size options, and delete what you no longer need. Region choice is permanent per database, so the read-only helpers here (region list, ping, size cluster list) are worth running before you create anything.
// databases & regions
8 commands$ pscale database create mydb --region us-east$ pscale database create mydb --engine postgresql --region gcp-asia-northeast3 --replicas 2$ pscale database list$ pscale database show mydb$ pscale database delete mydb$ pscale region list$ pscale ping$ pscale size cluster list// faq
Can pscale create Postgres databases, or only MySQL?
Both. `pscale database create` defaults to MySQL (Vitess); pass --engine postgresql for a Postgres database, plus optional --major-version and --replicas (0 for single node, 2+ for high availability). The engine determines which commands work later: connect, deploy-request, password, and keyspace are Vitess-only, while role and traffic-control are Postgres-only.
How do I pick the right region?
Run `pscale region list` to see the options, then `pscale ping` to measure real latency from your machine to every public PlanetScale edge. Put the database in the region closest to your application servers — not to you. The region is fixed at creation, so moving later means dump-and-restore into a new database.
Is `pscale database delete` recoverable?
No — it drops the database, all branches, and all data. The CLI asks you to type the database name to confirm; --force skips even that, so keep it out of scripts unless you're tearing down throwaway environments on purpose.