PostgreSQL is an open-source object-relational database with a reputation for being reliable. It's built to support both small applications and large enterprise ecosystems and everything in between.
PostgreSQL for All is a general introduction to PostgreSQL on Compose.
Are you wondering what you'll get, or can get, with a Compose PostgreSQL deployment? Want to know what you'll need to do to manage it? Check out some of the implementation features and details down in PostgreSQL for Ops and Admins.
Just deployed PostgreSQL and want to get coding with it? Developing an application or want to try a new stack? Then see the PostgreSQL for Developers section for resources on how to connect from different languages, command line tools and more information to get you started.
When deployed on Compose, PostgreSQL comes with these standard Compose features.
- Automatically scaling server stack that scales RAM, CPU, and I/O as your PostgreSQL data grows.
- Daily, weekly, monthly, and on-demand backups..
- Metrics displayed in the Compose UI.
- Deploy, manage, backup, and otherwise automate database tasks through The Compose API.
- Guaranteed resources per deployment.
- Daily logs available for download.
Compose deployments of PostgreSQL also come with a number of PostgreSQL specific features:
- Data Browser For PostgreSQL.
- An optional add-on for real-time log access.
- The ability to forward rich metrics to services with an optional add-on.
- Access to the standard contrib modules.
- No limit on database or schema creation - you have
- Prices start from $17.50 for a 1GB deployment and $12 per extra gigabyte.
All PostgreSQL Deployments are high-availability clusters with two data nodes, one etcd arbiter capsule, and one haproxy capsule for managing connections and fail-over. Each data node contains 1GB storage and 102MB of memory. The haproxy node has 64MB of memory.
On standard Compose Hosted deployments, automatic vertical scaling occurs as your data set grows. You can also manually scale up your portals and MongoDB deployment from the deployment's Resources panel. A 10:1 ratio of disk to RAM is maintained, so by increasing the disk allocated to the deployment, you increase the RAM allocated.
You may add additional TCP portals from the Security panel in the Compose UI, as well as scale them with more memory should you need it.
For more information, see the PostgreSQL Resources and Scaling page.
See Compose Datacenter Availability for current location availability.
Compose deployments are billed based on disk usage and your PostgreSQL deployment usage is measured hourly. It is then grouped into a single monthly billing cycle. This means that any scaling or add-on usage will be charged from when the new resource was provisioned; not just for the month. You can see your deployment's usage in the Overview panel, under Current Usage.
Initial deployment set up is $17.50/month. Depending on which scaling and add-ons options you choose, the cost will increase. For example, if you wish to add extra storage and RAM, it is billed at an additional $12/month per unit of 1GB storage/100MB memory, so an additional 2GB storage/204MB memory will cost an additional $24/month.
PostgreSQL clusters consist of a leader and a follower member on separate machines in separate zones. In the event of a leader member failure, we've configured automatic promotion of the current slave within 60 seconds of the leader becoming unresponsive. Failover will only occur if the follower is within 1 MB of the leader, else the deployment will wait for the leader to come online.
Each PostgreSQL deployment has a proxy, which provides a single member connection string so there's no worrying with which member is currently leader. Failover will happen seamlessly without requiring you to change your application's connection configuration.
Compose PostgreSQL backups use
pg_basebackup on your running database cluster to backup your entire deployment. It makes a binary copy of the cluster files and includes all files in the data directory and tablespaces. Also included in the backups is the WAL file any one backup will offer a full restore to that time.
General information on backup schedules, downloading, and restoring can be found on the Backups page.
Since your PostgreSQL backups are available for you to download, you may get a copy of your deployment running locally. To do so, you will need a local installation of PostgreSQL and the downloaded backup of your deployment. For using the backup, we include a README file which also provides instructions for using the backup file locally. Open the README file with any text editor.
The file structure of the backup allows for multiple backups to be stored in the same directory; the top few levels are data --> backup --> datestamp directory. Inside the datestamped directory is the snapshot and the WAL archive. You will want to start up your local PostgreSQL inside the snapshot directory with the command
postgres -D conf. You can then connect to the db by running:
psql postgres -U focker.
psql is the interactive terminal for PostgreSQL. You can install it locally and then use the connection strings and credentials from Compose to interact with your deployment. To install psql:
- Ubuntu: Run
sudo apt-get install postgresql-clientto install the psql command.
- Mac OS X:
- Other platforms: Consult the PostgreSQL download page for details of the various install options.
The Overview panel of the Compose UI provides the basic information you need to get connected to your databases. In the section Connection info you will find Credentials and Connection Strings for your application, including a psql command for connecting. For more information, including examples in many languages, see the Connecting to PostgreSQL page.
The full list of documentation for PostgreSQL is in the side-bar, in addition to all things Compose.
If this article didn't solve things, summon a human and get some help!