Overview

Single Node

• meta: Default single-node installation template with extensive configuration parameter descriptions.
• rich: Downloads all available PostgreSQL extensions and Docker, provisioning a series of databases for software backups.
• pitr: A single-node configuration sample for continuous backups and Point-in-Time Recovery (PITR) using remote object storage.
• demo: Configuration file used by the Pigsty demo site, configured to serve publicly with domain names and certificates.

Dual Node

• dual: Dual-node template to set up a basic high-availability PostgreSQL cluster with master-slave replication, tolerating the failure of one node.
• slim: Minimal installation that avoids setting up local software repositories or infrastructure, relying only on etcd for a highly available PostgreSQL cluster.
• pg16: A dual-node PostgreSQL cluster installation using PostgreSQL 16 as a substitute for the current default, PostgreSQL 17.
• supa: Uses Docker Compose to start Supabase on a local master-slave PostgreSQL cluster.

Three Node

• trio: Three-node configuration template providing a standard High Availability (HA) architecture, tolerating failure of one out of three nodes.
• safe: A three-node template with hardened security, following high-standard security best practices.
• infra: Deploys a three-node observability infrastructure to monitor other RDS PostgreSQL instances.
• minio: Installs a three-node high-availability MinIO cluster to provide S3-compatible object storage services.

Four Node

• full: A four-node standard sandbox demonstration environment, featuring two PostgreSQL clusters, MinIO, Etcd, Redis, and a sample FerretDB cluster.
• mssql: Replaces PostgreSQL with a Microsoft SQL Server-compatible kernel using WiltonDB or Babelfish.
• polar: Substitutes native PostgreSQL with Alibaba Cloud’s PolarDB for PostgreSQL kernel.
• ivory: Replaces native PostgreSQL with IvorySQL, an Oracle-compatible kernel by HighGo.