Version v2.7.0 of the documentation is no longer actively maintained. The site that you are currently viewing is an archived snapshot. For up-to-date documentation, see the latest version.
Category: Arch
-
Cluster Model
PGSQL for production environments is organized in clusters, which clusters are logical entities consisting of a set of database instances associated by primary-replica. Each database cluster is an autonomous serving unit consisting of at least one …
PGSQL for production environments is organized in clusters, which clusters are logical entities consisting of a set of database instances associated by primary-replica. Each database cluster is an autonomous serving unit consisting of at least one …
-
Architecture
Component Overview Here is how PostgreSQL module components and their interactions. From top to bottom: Cluster DNS is resolved by DNSMASQ on infra nodes Cluster VIP is manged by vip-manager, which will bind to cluster primary. vip-manager will …
Component Overview Here is how PostgreSQL module components and their interactions. From top to bottom: Cluster DNS is resolved by DNSMASQ on infra nodes Cluster VIP is manged by vip-manager, which will bind to cluster primary. vip-manager will …
-
Architecture
Modular Architecture and Declarative Interface! Pigsty deployment is described by config inventory and materialized with ansible playbooks. Pigsty works on Linux x86_64 common nodes, i.e., bare metals or virtual machines. Pigsty uses a modular …
Modular Architecture and Declarative Interface! Pigsty deployment is described by config inventory and materialized with ansible playbooks. Pigsty works on Linux x86_64 common nodes, i.e., bare metals or virtual machines. Pigsty uses a modular …