Next steps with PGD v5.6
Going further with your PGD cluster
Architecture
This quick start created a single region cluster of high-availability Postgres databases. This is the Always-on Single Location architecture, one of a range of available PGD architectures. Other architectures include Always-on Multi-Location, with clusters in multiple data centers working together, and variations of both with witness nodes enhancing resilience. See architectural options.
Postgres versions
This quick start deployed EDB Postgres Advanced Server to the database nodes. PGD can deploy three different kinds of Postgres distributions, EDB Postgres Advanced Server, EDB Postgres Extended Server, and open-source PostgreSQL. The selection of database affects PGD, offering different capabilities, depending on server.
- Open-source PostgreSQL doesn't support CAMO.
- EDB Postgres Extended Server supports CAMO but doesn't offer Oracle compatibility.
- EDB Postgres Advanced Server supports CAMO and offers optional Oracle compatibility.
Further reading
- Learn PGD's terminology, from asynchronous replication to write scalability.
- Find out how applications work with PGD and how common Postgres features like sequences are globally distributed.
- Discover how PGD supports rolling upgrades of your clusters.
- Take control of routing and use SQL to control the PGD proxies.
- Engage with the PGD CLI to manage and monitor your cluster.
Deprovisioning the cluster
When you're done testing the cluster, deprovision it.
tpaexec deprovision democluster
- With a Docker deployment, deprovisioning tears down the Docker containers, network, and other local configuration.
- With an AWS deployment, deprovisioning removes the EC2 instances, VPC configuration, and other associated resources. Note that it leaves the S3 bucket it created. You must manually remove it.