Managing PostgreSQL Clusters
Create/destroy PostgreSQL clusters, scale existing clusters, and clone clusters.
Create/destroy PostgreSQL clusters, scale existing clusters, and clone clusters.
Failover path triggered by node crash causing leader lease expiration and cluster election
Learn the parameter optimization strategies Pigsty uses for the 4 different PostgreSQL workload scenarios.
Trade-off analysis for RPO (Recovery Point Objective), finding the optimal balance between availability and data loss.
PostgreSQL primary process crashes while Patroni stays alive and attempts restart, triggering failover after timeout
PostgreSQL config template optimized for online transaction processing workloads
Entity-Relationship model for PostgreSQL clusters in Pigsty, including E-R diagram, entity definitions, and naming conventions.
Everything about PostgreSQL - development, administration, internals, ecosystem, tools, extensions, and best practices
Trade-off analysis for RTO (Recovery Time Objective), finding the optimal balance between recovery speed and false failover risk.
User management - create, modify, delete users, manage role membership, connection pool config
Database management - create, modify, delete, rebuild, and clone databases using templates
Detailed analysis of worst-case, best-case, and average RTO calculation logic and results across three classic failure detection/recovery paths
PostgreSQL config template optimized for online analytical processing workloads
PostgreSQL config template optimized for critical/financial workloads with data safety and audit compliance
Manage PostgreSQL cluster HA with Patroni, including config changes, status check, switchover, restart, and reinit replica.
Manage Pgbouncer connection pool, including pause, resume, disable, enable, reconnect, kill, and reload operations.
PostgreSQL config template optimized for micro instances and resource-constrained environments
Use systemctl to manage PostgreSQL cluster component services - start, stop, restart, reload, and status check.
Configure crontab to schedule PostgreSQL backups, vacuum freeze, and bloat maintenance tasks
Extension management - download, install, configure, enable, update, and remove extensions
Version upgrade - minor version rolling upgrade, major version migration, extension upgrade
Pigsty uses Patroni to implement PostgreSQL high availability, ensuring automatic failover when the primary becomes unavailable.
PostgreSQL module component interactions and data flow.
Pigsty uses pgBackRest to implement PostgreSQL point-in-time recovery, allowing users to roll back to any point in time within the backup policy window.
Pigsty uses HAProxy to provide service access, with optional pgBouncer for connection pooling, and optional L2 VIP and DNS access.
Authentication, access control, encrypted communication, audit logs—meeting SOC2 compliance requirements.
How Pigsty provides defense-in-depth across seven security layers, from physical security to user security.
Pigsty provides standard security practices with an out-of-the-box role and permission model.
Get started with PostgreSQL—connect using CLI and graphical clients
This article lists PostgreSQL extensions supported by Pigsty and their compatibility across different systems.
Deploy and manage world’s most advanced open-source relational database — PostgreSQL, customizable and production-ready!
Choose the appropriate instance and cluster types based on your requirements to configure PostgreSQL database clusters that meet your needs.
Choose the appropriate instance and cluster types based on your requirements to configure PostgreSQL database clusters that meet your needs.
How to choose the appropriate PostgreSQL kernel and major version.
Pigsty provides a package alias translation mechanism that shields the differences in binary package details across operating systems, making installation easier.
How to define and customize PostgreSQL users and roles through configuration?
How to define and customize PostgreSQL databases through configuration?
Detailed explanation of PostgreSQL and Pgbouncer Host-Based Authentication (HBA) rules configuration in Pigsty.
Default role system and privilege model provided by Pigsty
Split read and write operations, route traffic correctly, and reliably deliver PostgreSQL cluster capabilities.
Default role system and privilege model provided by Pigsty
Separate read and write operations, route traffic correctly, and deliver PostgreSQL cluster capabilities reliably.
Standard Operating Procedures (SOP) for database administration tasks
Users/roles refer to logical objects within a database cluster created using the SQL commands CREATE USER/ROLE.
Database refers to the logical object created using the SQL command CREATE DATABASE within a database cluster.
Detailed explanation of Host-Based Authentication (HBA) in Pigsty.
Default role system and privilege model provided by Pigsty
Common failures and analysis troubleshooting approaches
How to migrate an existing PostgreSQL cluster to a new Pigsty-managed PostgreSQL cluster with minimal downtime?
Step-by-step guides for common PostgreSQL tasks and scenarios.
Overview of Pigsty’s monitoring system architecture and how to monitor existing PostgreSQL instances
Pigsty provides numerous out-of-the-box Grafana monitoring dashboards for PostgreSQL
Pigsty provides many out-of-the-box Grafana monitoring dashboards for PostgreSQL
Complete monitoring metrics reference for the Pigsty PGSQL module
Complete list and explanation of monitoring metrics provided by the Pigsty PGSQL module
Handling accidental data deletion, table deletion, and database deletion
How to manage PostgreSQL clusters with Ansible playbooks
Harness the synergistic power of PostgreSQL extensions
HA scenario response plan: When two of three nodes fail and auto-failover doesn’t work, how to recover from the emergency state?
Vanilla PostgreSQL kernel with 440 extensions
How to deploy a Citus high-availability distributed cluster?
Percona Postgres distribution with TDE transparent encryption support
MySQL compatible Postgres 14 fork
Next-generation OLTP engine for PostgreSQL
Use Pigsty’s built-in Patroni config templates or customize your own
How to use other PostgreSQL kernel forks in Pigsty? Such as Citus, Babelfish, IvorySQL, PolarDB, etc.
Four-step process overview for using extensions
Core concepts of PostgreSQL extensions and the Pigsty extension ecosystem
Extension package aliases and category naming conventions
Download extension packages from software repositories to local
Install extension packages on cluster nodes
Preload extension libraries and configure extension parameters
Create and enable extensions in databases
Upgrade PostgreSQL extension versions
Uninstall PostgreSQL extensions
PostgreSQL extensions installed by default in Pigsty
Frequently asked questions about PostgreSQL
Pigsty extension software repository configuration
Miscellaneous Topics
Deploy native high-availability Citus horizontally sharded clusters with Pigsty, seamlessly scaling PostgreSQL across multiple shards and accelerating OLTP/OLAP queries.
Create Microsoft SQL Server compatible PostgreSQL clusters using WiltonDB and Babelfish! (Wire protocol level compatibility)
Use HighGo’s open-source IvorySQL kernel to achieve Oracle syntax/PLSQL compatibility based on PostgreSQL clusters.
Using Alibaba Cloud’s open-source PolarDB for PostgreSQL kernel to provide domestic innovation qualification support, with Oracle RAC-like user experience.
Using Alibaba Cloud’s commercial PolarDB for Oracle kernel (closed source, PG14, only available in special enterprise edition customization)
Deploy/Monitor Greenplum clusters with Pigsty, build Massively Parallel Processing (MPP) PostgreSQL data warehouse clusters!
Deploy/Monitor Cloudberry clusters with Pigsty, an MPP data warehouse cluster forked from Greenplum!
Use Neon’s open-source Serverless PostgreSQL kernel to build flexible, scale-to-zero, forkable PG services.