RPO Trade-offs
Trade-off analysis for RPO (Recovery Point Objective), finding the optimal balance between availability and data loss.
Module: PIGSTY
RTO Trade-offs
Trade-off analysis for RTO (Recovery Time Objective), finding the optimal balance between recovery speed and false failover risk.
About
Learn about Pigsty itself in every aspect - features, history, license, privacy policy, community events, and news.
Features
Pigsty’s value propositions and highlight features.
Roadmap
Future feature planning, new feature release schedule, and todo list.
History
The origin and motivation of the Pigsty project, its development history, and future goals and vision.
News & Events
News and events related to Pigsty and PostgreSQL, including latest announcements!
Join the Community
Pigsty is a Build in Public project. We are very active on GitHub, and Chinese users are mainly active in WeChat groups.
Privacy Policy
What user data does Pigsty software and website collect, and how will we process your data and protect your privacy?
License
Pigsty’s open-source licenses — Apache-2.0, AGPLv3, and CC BY 4.0
Sponsor Us
Pigsty sponsors and investors list - thank you for your support of this project!
User Cases
Pigsty customer and application cases across various domains and industries
Concepts
Understand Pigsty’s core concepts, architecture design, and principles. Master high availability, backup recovery, security compliance, and other key capabilities.
Subscription
Pigsty Professional/Enterprise subscription service - When you encounter difficulties related to PostgreSQL and Pigsty, our subscription service provides you with comprehensive support.
FAQ
Answers to frequently asked questions about the Pigsty project itself.
Architecture
Pigsty’s modular architecture—declarative composition, on-demand customization, flexible deployment.
ER Model
How Pigsty abstracts different functionality into modules, and the E-R diagrams for these modules.
Cost Reference
This article provides cost data to help you evaluate self-hosted Pigsty, cloud RDS costs, and typical DBA salaries.
Infra as Code
Pigsty uses Infrastructure as Code (IaC) philosophy to manage all components, providing declarative management for large-scale clusters.
High Availability
Pigsty uses Patroni to implement PostgreSQL high availability, ensuring automatic failover when the primary becomes unavailable.
Inventory
Describe your infrastructure and clusters using declarative configuration files
Configure
Use the configure script to automatically generate recommended configuration files based on your environment.
Parameters
Fine-tune Pigsty customization using configuration parameters
Conf Templates
Use pre-made configuration templates to quickly generate configuration files adapted to your environment
Use CMDB as Config Inventory
Use PostgreSQL as a CMDB metabase to store Ansible inventory.
Security and Compliance
Authentication, access control, encrypted communication, audit logs—meeting SOC2 compliance requirements.
Seven-Layer Security Model
How Pigsty provides defense-in-depth across seven security layers, from physical security to user security.
Access Control
Pigsty provides standard security practices with an out-of-the-box role and permission model.
Get Started
Deploy Pigsty single-node version on your laptop/cloud server, access DB and Web UI
Single-Node Installation
Get started with Pigsty—complete single-node install on a fresh Linux host!
Web Interface
Explore Pigsty’s Web graphical management interface, Grafana dashboards, and how to access them via domain names and HTTPS.
Customize Pigsty with Configuration
Express your infra and clusters with declarative config files
Run Playbooks with Ansible
Use Ansible playbooks to deploy and manage Pigsty clusters
Offline Installation
Install Pigsty in air-gapped env using offline packages
Slim Installation
Install only HA PostgreSQL clusters with minimal dependencies
Security Tips
Three security hardening tips for single-node quick-start deployment
Deployment
Multi-node, high-availability Pigsty deployment for serious production environments.
Install Pigsty for Production
How to install Pigsty on Linux hosts for production?
Prepare Resources for Serious Deployment
Production deployment preparation including hardware, nodes, disks, network, VIP, domain, software, and filesystem requirements.
Planning Architecture and Nodes
How many nodes? Which modules need HA? How to plan based on available resources and requirements?
Setup Admin User and Privileges
Admin user, sudo, SSH, accessibility verification, and firewall configuration
Sandbox
4-node sandbox environment for learning, testing, and demonstration
Vagrant
Create local virtual machine environment with Vagrant
Terraform
Create virtual machine environment on public cloud with Terraform
Security
Security considerations for production Pigsty deployment
References
Detailed reference information and lists, including supported OS distros, available modules, monitor metrics, extensions, cost comparison and analysis, glossary
Pigsty Modules
This article lists all available modules in Pigsty and the module roadmap.
File Hierarchy
How Pigsty’s file system structure is designed and organized, and directory structures used by each module.
Conf Templates
Batteries-included configuration templates for specific scenarios, with detailed explanations.
FAQ
Frequently asked questions about the Pigsty INFRA infrastructure module
FAQ
Frequently asked questions about Pigsty etcd module