Overview

Exoscale Managed PostgreSQL delivers a fully managed, high-availability deployment of the popular open-source database engine. The service is aimed at teams that need rock-solid ACID compliance, automated operations, and predictable performance without managing infrastructure themselves.

Terminology

  • Service
    A running PostgreSQL cluster managed by Exoscale DBaaS
  • Plan
    A size / redundancy tier (hobbyist-1, startup-4, business-32, premium-9x-16, …)
  • Fork
    A point-in-time clone of an existing service (used for upgrades, DR tests, etc.)
  • Read Replica
    A replica created through the DBaaS “read replica” integration
  • pgBouncer
    Built-in connection pooler that fronts every service for higher connection density

Features

  • Managed Cluster Lifecycle
    automated provisioning, patching and minor-version upgrades.
  • Automatic Daily Backups
    with user-defined retention and point-in-time recovery (PITR) on Business & Premium plans.
  • Vertical & Horizontal Scaling
    change plan size or add read replicas without downtime.
  • Connection Pooling
    pgBouncer is pre-configured for each service, reducing idle connection load.
  • High SLA
    99.95 % on Hobbyist / Startup, 99.99 % on Business / Premium plans.
  • CLI & API First
    every feature exposed via exo dbaas …; the Portal currently covers common workflows.

Availability

PostgreSQL is available in all current Exoscale zones.

ZoneCountryCityAvailability
at-vie-1AustriaVienna
at-vie-2AustriaVienna
ch-gva-2SwitzerlandGeneva
ch-dk-2SwitzerlandZurich
de-fra-1GermanyFrankfurt
de-muc-1GermanyMunich
bg-sof-1BulgariaSofia
hr-zag-1CroatiaZagreb

Limitations

  • Portal Feature Gap
    some advanced settings (e.g. custom pg- parameters, PITR window edits) are currently available only through the CLI or API.
  • No Cross-Engine Integrations
    direct replication between PostgreSQL and other DBaaS engines is not supported.
  • Single-Zone Clusters
    geo-replication is available via read-replica integration, but primary clusters live in one zone.
  • Super-User Access
    is restricted; extensions that require super-user rights must be requested via support.

NOTE
For operational procedures (backups, upgrades, maintenance windows, …) see the section Operation.
Hands-on guides (migrations, client libraries, Terraform modules, …) you can find under How-To.