sty

Decision date: 2026-10-04 Status: Released in v1.9.0. Current reference: pig repo Scope: Installing the existing embedded Pigsty public key during repository configuration. Decision When a selected module contains an available pigsty-infra or …

Decision date: 2026-08-14 Status: Implemented and released in pig v1.8.0. Current reference: pig sty boot Scope: Preparing a Pigsty controller and its package sources; not deploying a database cluster. Decision pig sty boot should be one native, …

Pig v1.8.0 makes Pigsty controller setup native. The two core setup commands, pig sty boot and pig sty conf, are now failure-aware Go workflows instead of wrappers around the legacy bootstrap and configure shell scripts. The release keeps the public …

Decision date: 2026-08-13 Status: Proposal for review; not implemented. Current reference: PIG documentation and release history Scope: Candidate product boundaries and verification gates for a future PIG 2.0 / Pigsty 5.0 line. Decision The proposed …

Pig v1.6.2 is a feature and catalog release on top of v1.6.1. It grows the packaged extension catalog from 562 to 572, adds native Grafana dashboard schema v2 support, and improves local repository generation. The embedded Pigsty version remains …

Decision date: 2026-07-18 Status: Released in v1.6.0; dashboard schema v2 support followed in v1.6.2. Current reference: pig sty grafana Scope: Dashboard import, export, cleanup, and selected organization and user preferences. Decision PIG uses a …

Decision date: 2026-07-18 Status: Released in v1.6.0 as an experimental adapter. The earlier revision-store design is superseded. Current reference: pig inventory cmdb Scope: Exchanging declarations with Pigsty’s existing CMDB, not designing another …

Decision date: 2026-07-18 Status: Implemented and released in pig v1.6.0. The 2026-10-16 to 2026-10-17 refinements below are Implemented in the v1.10.0 candidate, not yet released. Current reference: pig inventory Scope: Static Pigsty Inventory …

Six months ago, on January 8, 2026, I wrote Git for Data: Instant PostgreSQL Database and Instance Cloning, introducing a new feature in PostgreSQL 18 and Pigsty v4.0: instant database cloning. With filesystem copy-on-write (CoW) and PostgreSQL 18’s …

People often ask me: what exactly is Pigsty? My usual answer is: a PostgreSQL distribution. The next question is usually: what, then, is a “PostgreSQL distribution”? That is a good question. And the best place to begin is not databases, but operating …

Refresh the built-in extension catalog from 510 to 524 available extensions. This adds 14 extensions: pg_stl, pgmnemo, psql_bm25s, pg_orca, pg_sorted_heap, graph, pgrdf, fsm_core, jsonschema, pg_durable, pg_mockable, pg_uuid_v8, pg_stat_backtrace, …

Extension catalog and alias resolution enhancements: Introduce dynamic PG category alias resolution by PG major version. Add OS-level alias overrides (ansible/bootstrap) and converge unknown distro fallback to PGDG-only. Add aliases such as …

Decision date: 2026-02-18; the production contract was finalized on 2026-08-14. Status: Implemented and released in pig v1.8.0. Current reference: pig sty conf Scope: Generating one validated static Inventory from a trusted Pigsty template; not …

Fixes Preserve symlink semantics during build-tree migration and support cross-device moves. Handle a PostgreSQL log directory configured as the filesystem root without resolving files outside the intended directory. Allow pig repo rm to remove …

Changes Rename pig sty install to pig sty deploy so the command name reflects that it runs the Pigsty deployment playbook. Add the -g, -p, and -o options to pig sty conf, aligning it with the configure script available in this release. Keep llvmjit …

Update the extension list to 422 New extension: pgactive from AWS Bump timescaledb to 2.20.3 Bump citus to 13.1.0 Bump vchord to 0.4.3 Bug fix pgvectorscale debian/ubuntu pg17 failure Bump kubernetes repo to 1.33 Bump default pigsty version to 3.5.0 …

pig inventory (alias pig inv) inspects, edits, and validates the Pigsty inventory, pigsty.yml. It also checks deployment prerequisites and exchanges configuration with PostgreSQL through the experimental cmdb commands. When you edit a fragment, PIG …

pig do runs administration playbooks from the selected Pigsty directory. It uses the inventory to add clusters, create databases and users, install packages, or remove services. Define the target configuration in the inventory first, then run the …

pig sty installs Pigsty, prepares the controller, generates configuration, and runs deployment playbooks. It also manages dashboards through the Grafana HTTP API. Command Purpose sty init Download and extract Pigsty into an installation directory sty …