Use the Engine choice in PD DigitalOcean Databases to select PostgreSQL or MySQL and its DigitalOcean edition. Edition affects the plans and availability features you can offer.

Choose the edition on the offering

Open the database package on Module Options and select the intended PostgreSQL or MySQL Standard Edition or Advanced Edition. Save, then review that edition’s plans, versions and High availability before generating checkout choices. Do not assume a plan suitable for one edition is suitable for the other.

Apply the dated Standard Edition limits

For new clusters, DigitalOcean limits Standard Edition to at most 4 GiB RAM, without standby or read-only nodes. The restriction starts 15 October 2026 for accounts that have never created either PostgreSQL or MySQL, and 30 November 2026 for all accounts. Clusters created before the restriction applies to the account are not affected by that provider change.

Between those dates, the module cannot infer an account’s complete historical eligibility from its current clusters. A visible larger Standard Edition choice can therefore still be refused by DigitalOcean. From the all-account date, the module filters those over-limit new-cluster choices itself. Review older generated groups and their pricing before rebuilding.

See DigitalOcean’s dated PostgreSQL and MySQL plan changes for the current provider policy.

Match availability to the engine

The module’s Advanced PostgreSQL high-availability configuration uses two nodes; Advanced MySQL uses three. Kafka has its own three-broker base layout and no separate High availability choice. Other engines have their own supported layouts and size requirements. Extra nodes affect provider costs, and a plan label alone does not establish availability for your account and region.

Keep edition changes separate from resizing

An existing database keeps its engine and edition. Moving its service to an offering of another edition is refused rather than used as a conversion. Plan a new service and a separately managed data move when that is required; do not repeatedly retry a refused resize.

The client Backups page in this module is limited to Standard Edition PostgreSQL and MySQL. Its absence on Advanced Edition does not establish that the provider has no backups.

See the PD DigitalOcean Databases Blesta guide for related setup, or explore PD DigitalOcean Databases.