These are the frequently asked questions for Vultr Managed Databases for PostgreSQL.
Yes, all managed databases are backed up for disaster recovery purposes. In addition, all plans other than Hobbyist offer user-initiated recovery, forking, and point-in-time backups. You can use these backups to restore a cluster, which overwrites the current cluster's data. You can also fork a cluster from the backup, creating a new cluster with the backup data and not modifying the existing cluster. You'll find those options in the Actions section of your cluster's Overview tab.
PostgreSQL offers point-in-time recovery history, and the duration available depends on your node plan.
You can deploy managed databases in several node plans, which are a shorthand way of identifying the available size and number of nodes. We offer Hobbyist, Startup, Business, and Premium node plans.
After you deploy a managed database, look in the General Information section of your cluster's information page. The Node Plan appears below the Monthly Price. The plan name format is Vultr-Dbaas-[plan type]-[other internal information]
.
The node plan determines what backup and recovery options are available.
Yes you can deploy managed databases for PostgreSQL using the Vultr Customer Portal, Vultr API, or Vultr API.
Use the Change Plan menu on the Settings tab to scale your cluster up. To scale a cluster down, migrate or fork it to a new, smaller cluster.
You cannot create superuser accounts for managed databases. To create a standard user account, use the Vultr Customer Portal.
A cluster can only have one primary node, but you can have multiple replica (read-only) nodes.
Yes, you must use primary keys for all database tables, which is enforced through the database configuration.
Vultr Managed Databases for PostgreSQL supports PostgreSQL versions 13 through 16.
To enable or remove PostgreSQL extensions, connect to the database server with psql
and follow the steps below:
Check the available extensions.
SELECT * FROM pg_available_extensions;
Enable an extension.
CREATE EXTENSION extension_name;
Remove an extension.
DROP EXTENSION extension_name;