Managed databases

#What a managed database is

A managed database is a single PostgreSQL, MySQL or MariaDB server that we run for you. You choose the engine, the version and a size; we install it, keep it patched, give it a stable hostname and apply the access rules you set. You connect to it with your usual client, as the admin login you named.

• One server, one disk. Each database runs on its own virtual machine, sized by a plan: the plan's vCPUs and memory, and a data disk that starts at the plan's disk size. Choose a bigger disk at create, and grow it later without a restart. There is no replica or failover yet.
• Private only. A database never has a public address. It is reached from your own network, from the addresses its access rules and security groups allow: from a VM in its VPC in af-abj-2, or from a standard VPS with a private interface in af-abj-1.
• No shell. There is no SSH or console login to a database's machine. Everything you change, you change through the API: access rules and security groups, the password, storage, snapshots, power and deletion.
• Billed like a machine. A database costs what a VM in a VPC on the same plan costs, plus any storage beyond the plan's disk, with no management fee. It is paid for first. See pricing.

#Engines and versions

Only long-term-support lines are offered, and a new major version of PostgreSQL is added once it has had its first minor release.

You choose the version line; we apply its minor releases for you (see patching). A line is withdrawn from new databases at least six months before its upstream end of life, and moving to a new major version is never automatic.

What is on offer right now, and in which zone, is in the catalogue. Each version lists its end-of-life date and the zones it can be created in:

$ curl https://api.pantechdynamics.com/public/v1/database-engines \    -H "Authorization: Bearer $PANTECH_API_KEY"

A version that is not listed there, or not listed for your zone, cannot be created yet.

#The admin login

Each database has one admin login, named when you create it (dbadmin unless you choose another; a database created before the name could be chosen has pantech_admin). Its admin_username field always says which. It is deliberately not a superuser, so it cannot run commands on the machine or change the access configuration behind the access rules.

#Lifecycle

A database is running, stopped or deleted. Stop and start it from its page in the console, the API or the CLI, like a machine; a stopped database keeps its data and still pays for its disk.

To delete one in the console, turn Deletion protection off in its Danger zone, press Delete and type its name. Its data disk is destroyed 12 hours later, and nothing can bring it back after that.

Deleting a database removes its hostname first, then its machine and data disk. Billing stops, and the part of its upfront payment not yet deducted from a bill goes back to your credit balance; see pricing. Take a dump first if you might need the data. Its snapshots are not deleted with it: they stay, and stay billed, until you delete them.

#Limits

#Next