PostgreSQL
PostgreSQL is a powerful, open-source object-relational database system that combines the reliability and robustness of traditional relational databases with advanced features for modern applications. Known as "the world's most advanced open-source relational database," PostgreSQL excels in handling complex queries, maintaining strict ACID compliance for data integrity, and supporting both structured and semi-structured data through native JSON capabilities.
Through Viduli's Orbit Database Service, PostgreSQL becomes even more powerful with enterprise-grade managed features including automated backups, high availability configurations, and seamless scaling. Whether you're building traditional web applications, analytics platforms, or modern microservices architectures, PostgreSQL on Orbit provides the performance, reliability, and flexibility your applications demand without the operational overhead of self-managed database infrastructure.
Launching a New PostgreSQL Cluster
Creating a new PostgreSQL cluster is a streamlined process that provides you with a production-ready database environment within minutes. To launch a new cluster:
- Navigate to your project overview page
- Click the
New Resource
button in the sidebar - Select
Orbit
from the resource creation dialog - Choose
PostgreSQL
as your database engine - Configure your cluster settings including compute resources, storage, and networking options (detailed configuration options available in our configuration guide)
- Review the cost estimates and click
Confirm
to create your cluster
Provisioning Process: Your PostgreSQL cluster will automatically begin provisioning with the specified configuration. This process typically takes a few minutes as Orbit sets up the database instances, configures networking, and initializes the database system. Once provisioning completes, your cluster will be ready to accept connections and handle database operations.
Cost Transparency: The resource creation dialog displays both the minimum guaranteed cost and maximum potential cost with read replicas, helping you understand the financial impact of your configuration choices before deployment.
Starting a PostgreSQL Cluster
When your PostgreSQL cluster is in a stopped
state, you can bring it online to begin accepting database connections and serving queries. Starting a cluster transitions it to the running
state where it will actively consume resources and incur operational costs.
To start your cluster:
- Select your cluster from the project overview
- Verify the right sidebar displays your cluster details
- Click the start (play) icon in the cluster controls
- Wait for the startup process to complete
Startup Time: PostgreSQL clusters typically start within a few minutes as the database engine initializes, performs recovery procedures if needed, and becomes ready to accept connections.
Stopping a PostgreSQL Cluster
Stopping a running cluster immediately ceases database operations and resource consumption, which is useful for maintenance, cost optimization, or when temporarily suspending database availability.
To stop your cluster:
- Select your cluster from the project overview
- Ensure the right sidebar shows your cluster details
- Click the stop (square) icon in the cluster controls
- Wait for the shutdown process to complete
Shutdown Process: PostgreSQL clusters typically stop within a few minutes as Orbit gracefully terminates database connections, completes any pending transactions, and safely shuts down the database instances.
Cost Savings: Stopped clusters consume no compute resources and incur zero operational costs, making this an effective way to reduce expenses during periods when your database isn't needed. Storage costs continue to apply to preserve your data.
Deleting a PostgreSQL Cluster
Permanent deletion removes your PostgreSQL cluster and all associated data from Viduli. This action is irreversible and should only be performed when you're certain the database is no longer needed and you have proper backups if required.
To delete your cluster:
- Select your cluster from the project overview
- Verify the right sidebar displays your cluster details
- Click the delete (red bin) icon in the top-right corner
- In the confirmation dialog, type the exact resource name to confirm deletion
- Click
Confirm
to proceed with deletion
Deletion Process: Once confirmed, your cluster enters the deleting
state where no further actions can be performed. The complete removal process typically takes several minutes as all database instances, storage volumes, and associated resources are permanently destroyed.
Irreversible Action: Once a cluster enters the deleting
state, the process cannot be stopped or reversed. All database data, configurations, backups, and associated resources will be permanently destroyed. Ensure you have exported any critical data before proceeding with deletion.
Alternative Access: Cluster controls can also be accessed from the resource details view for additional management options and monitoring capabilities.
Configuring a PostgreSQL Cluster
To configure your PostgreSQL cluster settings, access the detailed configuration options through the cluster details view. This interface provides comprehensive control over your cluster's compute resources, storage settings, networking configuration, and operational parameters.
To access cluster configuration:
- Select your PostgreSQL cluster from the project overview
- Open the cluster details view by double-clicking the cluster or using the sidebar options
- Navigate to the Configuration tab within the details interface
Cluster Details View
The cluster details view can be accessed by following the instructions on the resources page.
PostgreSQL cluster details views include all the standard tabs discussed in the resources page, with the addition of a specialized Backup tab for database-specific operations.
Monitoring
Logs
See resource logs
Shell
Shell sessions for PostgreSQL clusters open directly into the psql
shell; you cannot access a general-purpose shell outside of the PostgreSQL client.
Actions
See resource actions section for commonly supported actions.
Additionally, database clusters have the Restore
action, which is triggered when restoring a database.
Environment
See resource environment for common environment behaviours.
Database clusters automatically export a set of environment variables containing connection and configuration details to the project environment. These exported variables are made available to all resources within the same project.
After deploying a cluster, you must redeploy any dependent resources for the exported environment variables to take effect.
Configuration
The database can be reconfigured while it is running. In most cases, configuration changes are applied with zero downtime; however, some changes may require a brief period of downtime.
For a primer on resource configuration, see the resource configuration page.
A comprehensive list of configuration options is available in the main article.
Costs
See resource costs
Backup
- The Backup tab displays the current backup retention period for the cluster.
- It provides an option to initiate a restore operation. The restore process supports point-in-time recovery (PITR) within the limits of the configured backup retention window.