cli

Pig v1.10.0 strengthens the correctness and safety of existing commands. It verifies PostgreSQL targets before operations, preserves Inventory sources and YAML types, and makes repository, extension, and automation results match the work actually …

Decision date: 2026-10-16 Status: Implemented in the v1.10.0 candidate, not yet released. Current reference: pig ext catalog count Scope: Catalog totals and default listing membership; package installation and SQL activation rules remain defined by …

Pig v1.9.0 adds one-command Xray client/server setup, automatic Pigsty repository-key preparation, and a refreshed 600-entry extension catalog. The default cargo-pgrx version is now 0.19.3; the embedded Pigsty version remains 4.5.0. Xray clients and …

Decision date: 2026-10-05 Status: Released in v1.9.0. The 2026-10-16 refinements below are Implemented in the v1.10.0 candidate, not yet released. Current reference: pig build, operations safety, and release history Scope: One-command Xray client …

Decision date: 2026-09-03 Status: Released in v1.8.1. Current reference: pig build Scope: Debug-package policy for pig build ext and pig build pkg; individual package recipes remain authoritative for their payload. Decision pig build ext and pig …

Pig v1.8.1 is a safety, correctness, and maintenance release on top of v1.8.0. It hardens command initialization, privileged log access, repository and build workflows, release integrity, and structured-output redaction. It also refreshes the …

Decision date: 2026-08-13 Status: Proposal; security mechanism, overlays, packaging, and path layout remain open. Current reference: pig ext and pig repo describe the v1 Catalog behavior. Scope: A candidate PIG 2.0 publication and consumption model …

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.0 is a major release: pig pt becomes a transparent patronictl launcher, the new root-level pig inventory command group brings lossless editing and validation of pigsty.yml (with an experimental PostgreSQL CMDB bridge), pig sty grafana adds …

Decision date: 2026-07-21 Status: Implemented and released in pig v1.6.0. Current reference: pig pt Scope: Patronictl-backed cluster commands plus PIG-owned configuration selection, settings sugar, service, status, and log helpers. Decision pig pt …

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 …

Decision date: 2026-07-02 Status: Released for pg, pb, pt, and pitr by v1.5.0; the 2026-08-29 do and build proxy refinements were released in v1.8.1. The acceptance refinements below are Implemented for v1.10.0; source evidence is listed under …

Decision date: 2026-06-30 Status: Implemented; the repository uses this layout for new commands. Current reference: pig command overview and the source repository Scope: Go source ownership and command registration, not the public command taxonomy …

This release is a focused engineering update from v1.2.0 to v1.3.0: 15 commits, 74 files changed, +1184 / -236 LOC. It hardens the pig build pipeline and extends catalog/alias coverage, increasing total extensions from 451 to 461. Highlights Build …

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 …

This release upgrades the CLI architecture from v1.0.0 to v1.1.0 (79 commits, 193 files changed), with the core goal of moving pig from a “human-friendly CLI” to an “agent-native orchestratable CLI”. Seven new extensions are added, bringing the total …

Decision date: 2026-02-12 Status: Released in pig v1.1.0 and refined by later command-layer work. The 2026-10-16 refinements below are Implemented in the v1.10.0 candidate, not yet released. Current reference: pig command overview Scope: PIG-owned …

WeChat link PostgreSQL’s killer feature is extensibility. PostGIS, pgvector, pg_duckdb, pg_search—extensions turn PG into GIS engine, vector DB, analytics warehouse, search cluster. But compiling and shipping them reliably across distros is a …

PIG is a Go command-line tool for installing PostgreSQL and extensions through the system package manager. It selects packages for the operating system, CPU architecture, and PostgreSQL version, then uses APT, YUM, or DNF to install them. The …

Use pig pe to read metrics from a running pg_exporter and reload its configuration. The full command name is pig pg_exporter. Aliases are pe, pgexp, and pgexporter. pig pe get # Show PostgreSQL metrics pig pe list # List PostgreSQL metric families …

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 manages PostgreSQL packages, local database services, and Pigsty deployments. Choose a command below for your task. Use pig COMMAND --help to see the options supported by your installed program. pig repo: manage software repositories pig ext: …