postgres on PIG

The 70% Tuner: Defining the Boundary of pig pg tune

Sat, 21 Mar 2026 00:00:00 +0000

Decision date: 2026-03-21
Status: Implemented on 2026-03-23 and released in pig v1.3.2.
Current reference: pig pg tune
Scope: A deterministic first-pass configuration for one local PostgreSQL instance, not a complete production design service.

Decision

pig pg tune should answer one bounded question: given a CPU count, memory size, disk size, and a workload profile, what are sensible core PostgreSQL parameters for this machine?

The command targets a “70% correct” starting point. It detects hardware when possible, accepts explicit overrides, calculates a small set of high-impact parameters, and can write them to postgresql.auto.conf. It does not claim to design replication, durability, security, logging, extensions, connection pooling, or workload-specific SQL behavior.

pig v1.5.0

Sat, 04 Jul 2026 00:00:00 +0000

Pig v1.5.0 is a PostgreSQL operations release for day-to-day DBA work. It adds local database clone/fork workflows, clarifies the boundaries between pg, pt, pb, and pitr, and tightens preview, confirmation, and structured-output behavior for high-risk operations.

Highlights

pig pg is now more focused on local PostgreSQL operations. pig pg clone creates quick database-level copies, while pig pg fork creates disposable physical instance forks for local validation, recovery drills, and isolated experiments.
Recovery flows are split more clearly: pig pitr is the orchestration entry point across Patroni, PostgreSQL, and pgBackRest; pig pb restore remains the low-level pgBackRest restore primitive. Restore commands now require an explicit target and provide more concrete plans and post-restore guidance.
Patroni operations are more predictable: high-risk actions such as pig pt restart, reinit, switchover, and failover use Pig-managed confirmation and plan output; pig pt config pg points operators to pig pt restart --pending when a restart is required.
Automation is safer: structured output no longer implies confirmation for destructive commands. High-risk execution requires explicit -y/--yes, while --plan and next_actions are more consistent for preview-then-execute workflows.
Logs and status output are more useful during incidents: pg, pb, and pt log commands now cover common latest / tail / show / grep workflows, and structured log snapshots use JSONL semantics.
Build and release defaults were refreshed: Pig is 1.5.0, embedded Pigsty is 4.4.0, and pig build pgrx defaults to cargo-pgrx 0.19.1.

Extension Catalog

Available extensions: 524 -> 531, with no removals.
New extensions: pg_ducklake, pgdisablelogerror, pg_stat_log, pg_stat_plans, passwordpolicy, db2fce, plpgsql_wrap.
Refreshed a batch of existing extension versions and package metadata, including timescaledb 2.28.2, postgis 3.6.4, vector 0.8.4, biscuit 2.4.1, citus 14.1.0, orioledb 1.8, documentdb 0.113, credcheck 5.0, and pgtt 4.5.
orioledb aliases no longer pin to PG17; they resolve against the requested PostgreSQL major. EL9 ARM64 Patroni aliases now point to noarch packages.

Compatibility Notes

Use -y/--yes for destructive operations in automation; structured output mode no longer substitutes for human confirmation.
pig pb restore and pig pitr require exactly one explicit recovery target; use --target-action=promote for auto-promote behavior.
Several ambiguous short options were cleaned up. For log commands, -o json means a JSONL snapshot and is not used for tail/follow streaming modes.

Checksums

| File | Checksum | | --- | --- | | [pig\-1\.5\.0\-1\.aarch64\.rpm](https://github.com/pgsty/pig/releases/download/v1.5.0/pig-1.5.0-1.aarch64.rpm) | SHA-256 · `9f83b78ed2eccedd55a86c634f88364f1945c3cefa1b23efdd72a7cf2062e1df` | | [pig\-1\.5\.0\-1\.x86\_64\.rpm](https://github.com/pgsty/pig/releases/download/v1.5.0/pig-1.5.0-1.x86_64.rpm) | SHA-256 · `b792001498e9907d4659db46640f9c5164152b20689f90f93418f76fb4633e6e` | | [pig\-v1\.5\.0\.darwin\-amd64\.tar\.gz](https://github.com/pgsty/pig/releases/download/v1.5.0/pig-v1.5.0.darwin-amd64.tar.gz) | SHA-256 · `ae1081dfbff8564ecdf713c85e8025c91bfd38e6575ea9ac99a92f968ab8a29d` | | [pig\-v1\.5\.0\.darwin\-arm64\.tar\.gz](https://github.com/pgsty/pig/releases/download/v1.5.0/pig-v1.5.0.darwin-arm64.tar.gz) | SHA-256 · `6d69efcdcdc79fd90d2112e1e8042887020402aa037252d89d632243e7085dc6` | | [pig\-v1\.5\.0\.linux\-amd64\.tar\.gz](https://github.com/pgsty/pig/releases/download/v1.5.0/pig-v1.5.0.linux-amd64.tar.gz) | SHA-256 · `8f914821b317cde73d3aec4ed311d5e90710bbc8cb372c1de3322083c31f4a85` | | [pig\-v1\.5\.0\.linux\-arm64\.tar\.gz](https://github.com/pgsty/pig/releases/download/v1.5.0/pig-v1.5.0.linux-arm64.tar.gz) | SHA-256 · `d4de9ef1c28d0a3661c4a4d47c469b7bfd5f5bddb610325796afb669ab162234` | | [pig\_1\.5\.0\-1\_amd64\.deb](https://github.com/pgsty/pig/releases/download/v1.5.0/pig_1.5.0-1_amd64.deb) | SHA-256 · `35fd32affb4cb5bcca845d47a768782fb7005f06fcc1bcb5b7755d2627f96245` | | [pig\_1\.5\.0\-1\_arm64\.deb](https://github.com/pgsty/pig/releases/download/v1.5.0/pig_1.5.0-1_arm64.deb) | SHA-256 · `2be1df804d3f630560bc3ced0107c49ffad8bb52b004f72c7f8b4d09dc8d3e04` |

v1.5.0 · 2026-07-04

One Grammar for Dangerous Work: PIG's Operations CLI Safety Contract

Thu, 02 Jul 2026 00:00:00 +0000

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.
Current reference: pig pg, pig pb, pig pitr, pig do, and pig build
Scope: PIG-owned operational commands; transparent upstream commands retain upstream confirmation and exit behavior.

Decision

Operational convenience must not blur operational meaning. PIG distinguishes low-level primitives from multi-stage orchestrators, makes destructive intent explicit, reserves aliases carefully, and requires plans and structured results to describe the same action that text mode will execute.

pig v1.3.2

Mon, 23 Mar 2026 00:00:00 +0000

Routine maintenance release.

Refresh a batch of extension version metadata and catalog entries.
Add the pig pg tune subcommand to generate PostgreSQL tuning parameters from hardware resources and workload profiles.
Add pdu and pgdog source package aliases for pig build get.
Migrate extension catalog URLs from pgext.cloud to pigsty.io/ext.

Checksums

| File | Checksum | | --- | --- | | [pig\-1\.3\.2\-1\.aarch64\.rpm](https://github.com/pgsty/pig/releases/download/v1.3.2/pig-1.3.2-1.aarch64.rpm) | SHA-256 · `d760f47652ff3e2e4a61eb7b9a68ca68665b2b36c187c52f5eaf50d2f007d8f3` | | [pig\-1\.3\.2\-1\.x86\_64\.rpm](https://github.com/pgsty/pig/releases/download/v1.3.2/pig-1.3.2-1.x86_64.rpm) | SHA-256 · `c2e02e62497f4c2055a9b448ddb3a24c618fcd488580c28b2b9a0e7cedacef55` | | [pig\-v1\.3\.2\.darwin\-amd64\.tar\.gz](https://github.com/pgsty/pig/releases/download/v1.3.2/pig-v1.3.2.darwin-amd64.tar.gz) | SHA-256 · `b8d066ddefa4530946c74c30e7e4acdab6abf8da70a47dcfe2a77719b79e397f` | | [pig\-v1\.3\.2\.darwin\-arm64\.tar\.gz](https://github.com/pgsty/pig/releases/download/v1.3.2/pig-v1.3.2.darwin-arm64.tar.gz) | SHA-256 · `a90e78d879fd720fd2865870c696aed7952558d5ae75591deced3121f2aab1f9` | | [pig\-v1\.3\.2\.linux\-amd64\.tar\.gz](https://github.com/pgsty/pig/releases/download/v1.3.2/pig-v1.3.2.linux-amd64.tar.gz) | SHA-256 · `2fe3a9ffbb6383154dfd25ed79420b210828eabf6a96a8af6e8feb9d744b9559` | | [pig\-v1\.3\.2\.linux\-arm64\.tar\.gz](https://github.com/pgsty/pig/releases/download/v1.3.2/pig-v1.3.2.linux-arm64.tar.gz) | SHA-256 · `522290aaf14f98f0bae83ce75cc76749f2a4e72742eb5c3cba36a1d2fa4d12c2` | | [pig\_1\.3\.2\-1\_amd64\.deb](https://github.com/pgsty/pig/releases/download/v1.3.2/pig_1.3.2-1_amd64.deb) | SHA-256 · `d6c1cf2c52962045f6bbfb2a669058e7f903088526591d6c939e7723f3928d30` | | [pig\_1\.3\.2\-1\_arm64\.deb](https://github.com/pgsty/pig/releases/download/v1.3.2/pig_1.3.2-1_arm64.deb) | SHA-256 · `4352385c629b26a1837054445a546da89591499848b557699c2fb70fde9377aa` |

v1.3.2 · 2026-03-23

pig v1.0.0

Mon, 26 Jan 2026 00:00:00 +0000

This release introduces three major new subcommand groups (pig pg, pig pt, pig pb) for managing PostgreSQL, Patroni, and pgBackRest, along with an orchestrated PITR command and enhanced extension availability display.

New Commands

pig pg - PostgreSQL instance management
- pg init/start/stop/restart/reload/status - Control and manage PostgreSQL instances
- pg role/promote - Detect and switch instance role (primary/replica)
- pg psql/ps/kill - Connection and session management
- pg vacuum/analyze/freeze/repack - Database maintenance operations
- pg log - Log viewing (list/tail/cat/less)
pig pt - Patroni cluster management

pig postgres

Mon, 01 Jan 0001 00:00:00 +0000

The pig pg command (alias pig postgres) manages local PostgreSQL servers and databases. It wraps local primitives such as pg_ctl, psql, and vacuumdb; use pig pt for Patroni cluster operations and pig pitr for orchestrated PITR.

pig pg - Local PostgreSQL primitives (pg_ctl / psql / local files).

Server Control (via pg_ctl):
  pig pg init     [-v ver] [-D datadir]     initialize data directory
  pig pg start    [-D datadir]              start PostgreSQL server
  pig pg stop     [-D datadir] [-m fast]    stop PostgreSQL server
  pig pg restart  [-D datadir] [-m fast]    restart PostgreSQL server
  pig pg reload   [-D datadir]              reload configuration
  pig pg status   [-D datadir]              show server status
  pig pg promote  [-D datadir]              promote standby to primary
  pig pg role     [-D datadir] [-V]         detect instance role (primary/replica)

Service Management (via systemctl):
  pig pg svc start                          start postgres systemd service
  pig pg svc stop                           stop postgres systemd service
  pig pg svc restart                        restart postgres systemd service
  pig pg svc reload                         reload postgres systemd service
  pig pg svc status                         show postgres service status

Connection & Query:
  pig pg psql     [db] [-c cmd]             connect to database via psql
  pig pg ps       [-a] [-u user]            show current connections
  pig pg kill     [-x] [-u user]            terminate connections (dry-run by default)
  pig pg clone    <src> [dst]               clone database with CREATE DATABASE TEMPLATE

Database Maintenance:
  pig pg vacuum   [db] [-a] [-t table]      vacuum tables
  pig pg analyze  [db] [-a] [-t table]      analyze tables
  pig pg freeze   [db] [-a] [-t table]      vacuum freeze tables
  pig pg repack   [db] [-a] [-t table]      repack tables (online rebuild)

Tuning:
  pig pg tune     [-p profile]     generate optimized parameters

Instance Fork:
  pig pg fork init <name> [-D datadir]      fork PGDATA into /pg/data-<name>
  pig pg fork list                          list managed forks
  pig pg fork start|stop|rm <name>          manage fork lifecycle

Utilities:
  pig pg log <list|tail|cat|less|grep>      view PostgreSQL logs

Command Overview

Service Control (pg_ctl wrapper):

pig pe

Mon, 01 Jan 0001 00:00:00 +0000

pig pe (aliases: pgexp, pgexporter) is a legacy convenience wrapper for a running pg_exporter. It reads the default metrics and statistics endpoints and can request a configuration reload. It is not a general or versioned pg_exporter client.

pig pe get                     # print pg_ metrics
pig pe list                    # list metric families from HELP lines
pig pe stat                    # print exporter statistics
pig pe reload                  # request configuration reload

Endpoint selection

The default endpoint is http://127.0.0.1:9630. Select another exporter with persistent options:

Instantly Clone PostgreSQL Databases—No Black Magic Required

Mon, 06 Jul 2026 00:00:00 +0000

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 new file_copy_method = clone setting, you can clone a huge database in seconds without consuming additional storage.

This is a particularly good fit for AI agents. As I wrote in What Kind of Database Do AI Agents Need?, ultra-low-cost database cloning is critical for counterfactual experiments. So when Pigsty 4.0 shipped, I added this capability to its PostgreSQL database provisioning workflow.

What Is a PostgreSQL Distribution?

Sat, 04 Jul 2026 00:00:00 +0000

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 systems.

I. Start with Linux Distributions

When most people hear “distribution,” they think of Linux distributions: Red Hat, Debian, Ubuntu, SUSE, Arch, and so on. But if Linux already exists, why do we need Linux distributions? What exactly is the relationship between the two?

Forging a China-Rooted, Global PostgreSQL Distro

Thu, 27 Nov 2025 00:00:00 +0000

Hi, I’m Feng Ruohang, author of Pigsty and an independent open-source contributor. Let’s talk about how to build a PostgreSQL distribution that is rooted in China and useful to the whole world.

The question isn’t whether PG will win—it already has. The question is: What role do we play in that victory? Spectator or protagonist? Follower or leader?

Why now

PostgreSQL is the default database

Stack Overflow’s 2025 survey shows 58.2% of professional developers use PG—18.6 points ahead of MySQL, and the gap is widening. New SaaS, AI startups, even OpenAI default to PG. DB-Engines rankings and JetBrains surveys tell the same story.

Pig, The Postgres Extension Wizard

Sun, 29 Dec 2024 00:00:00 +0000

Ever wished installing or upgrading PostgreSQL extensions didn’t feel like digging through outdated readmes, cryptic configure scripts, or random GitHub forks & patches? The painful truth is that Postgres’s richness of extension often comes at the cost of complicated setups—especially if you’re juggling multiple distros or CPU architectures.

Enter Pig, a Go-based package manager built to tame Postgres and its ecosystem of 440+ extensions in one fell swoop. TimescaleDB, Citus, PGVector, 20+ Rust extensions, plus every must-have piece to self-host Supabase — Pig’s unified CLI makes them all effortlessly accessible. It cuts out messy source builds and half-baked repos, offering version-aligned RPM/DEB packages that work seamlessly across Debian, Ubuntu, and RedHat flavors. No guesswork, no drama.