Skip to content

Choreo-Managed PostgreSQL Databases and Vector Databases

PostgreSQL on Choreo offers fully Choreo-managed, efficient object-relational databases on AWS, Azure, GCP, and Digital Ocean. Additionally, Choreo allows you to create fully-managed PostgreSQL vector databases if you want to perform efficient vector similarity search.

These services run on infrastructure and automation provided by Aiven, our technology partner and data platform subprocessor. For details on the partnership, SLA, and security posture, see the overview (./choreo-managed-databases-and-caches.md#technology-partnership).

Create a Choreo-managed PostgreSQL database

Follow the steps below to create a Choreo-managed PostgreSQL database:

  1. Sign in to the Choreo Console.
  2. In the header, click the Organization list. This opens the organization home page.
  3. In the left navigation menu, click DB & Services and then Databases.
  4. Click Create and select PostgreSQL as the database type. Provide a display name for this server and follow the instructions.
  5. Select your preferred cloud provider from AWS, Azure, GCP, or Digital Ocean.
    • The cloud provider is used to provision the compute and storage infrastructure for your database.
    • There is no functional difference between databases created on different cloud providers, apart from changes to service plans (and associated costs).
  6. Choose the region for your database.
  7. Available regions will depend on the selected cloud provider. Choreo currently supports US and EU regions across all providers.
  8. Select the service plan.
  9. Service plans vary in the dedicated CPU, memory (RAM), storage space allocated for your database, the backup retention periods, and high-availability configurations for production use cases.

Create a Choreo-managed PostgreSQL vector database

Follow the steps below to create a Choreo-managed PostgreSQL vector database:

  1. Sign in to the Choreo Console.
  2. In the header, click the Organization list. This opens the organization home page.
  3. In the left navigation menu, click DB & Services and then Vector Databases.
  4. Follow steps 4 onwards in the Create a Choreo-managed PostgreSQL database section.

Note

Once the database is created, you can add it to the marketplace so developers can discover these databases and use them in their applications. For more details, see Add Choreo-Managed Databases and Caches to the Marketplace.

Connecting to your Choreo-managed PostgreSQL database

To connect to your Choreo-managed PostgreSQL database, consider the following guidelines:

  • PostgreSQL databases accept traffic from the internet by default. You can restrict access to specific IP addresses and CIDR blocks under Advanced Settings.
  • You can use any PostgreSQL driver, ORM, or supported generic SQL library (may depend on the programming language) to connect to the database.
  • The connection parameters can be found in the Overview section in the Choreo Console under the relevant database.

High Availability and Automatic Backups

The high availability characteristics and the automatic backup retention periods for Choreo-managed PostgreSQL databases vary based on the selected service plan as shown below.

Service Plan High Availability Backup Retention Time Multi-AZ Deployment
Hobbyist Single-node with limited availability None No
Startup Single-node with limited availability 2 days No
Business Two-node (primary + standby) with higher availability 14 days Yes*
Premium Three-node (primary + standby + standby) with highest availability 30 days Yes*

*Multi‑AZ availability depends on the cloud provider and region and is enabled where supported.

Service plans with standby nodes are generally recommended for production scenarios for multiple reasons: - Provides another physical copy of the data in case of hardware, software, or network failures. - Typically reduces the data loss window in disaster scenarios. - Provides a quicker time to restore with a controlled failover in case of failures, as the standby is already installed and running.

Automatic Backups

  • Daily full backups of PostgreSQL databases are taken automatically
  • Write‑ahead logs (WAL) are copied periodically to support recovery
  • All backups are encrypted at rest

  • Backups are managed automatically during recovery; manual backup point selection is not supported

  • Choreo automatically handles outages and software failures by replacing broken nodes with new ones that resume correctly from the point of failure. The impact of a failure will depend on the number of available standby nodes in the database.

Failure Recovery

  • Minor failures (e.g., process restarts or transient network issues) are handled automatically without requiring changes to the deployment
  • For severe failures (e.g., node loss), monitoring detects the issue and schedules a replacement node automatically
  • In database failover scenarios, the Service URI remains the same; the IP address changes to point to the new primary node
  • For single‑node tiers, the service is unavailable during restoration and some recent writes may not be recoverable

Typical outcomes in multi‑node tiers include automatic failover within minutes and recovery workflows designed to minimize data loss.

Monitoring and Observability

  • Runtime metrics (CPU, memory, disk, network) and PostgreSQL logs are available in the Choreo Console
  • Native alerting for resource spikes is not currently available; contact Choreo support if you need to export metrics to third‑party monitoring

Connection limits

The following connection limits apply to Choreo-managed PostgreSQL databases based on the selected service plan.

Service Plan Max Connections
Hobbyist 25
Startup/Business/Premium-4 100
Business-16 400
Premium-8 200