THE POSTGRESQL EXTENSION PACKAGE MANAGER

Postgres Install Genius

Any extension. One command. 562 packaged extensions, across PostgreSQL 14-18.

pig does not replace apt or dnf — it drives them. Native RPM / DEB packages, built by Pigsty.

Get Started Documentation

$ pig install pg_duckdb -v 18

PIG // ONE LAYER ABOVE APT AND DNF pig install

APTdebDEBIAN · UBUNTU

NAME · VERSION · ARCH PIG RESOLVE · INSTALL

YUMrpmEL 8 · 9 · 10

CATALOG // 562 PACKAGED EXTENSIONS

postgisPG14-18vectorPG14-18timescaledbPG14-18pg_duckdbPG14-18

5 MB STATIC BINARYMAINTAINED BY PIGSTY

COVERAGE

562 Extensions, Every Supported Combination

562 Packaged Extensions 5 PostgreSQL Majors (14-18) 10 Linux Distro Majors × 2 Arches 0 Runtime Dependencies

QUICK START

Three Commands to a Working Extension

From a bare host to pg_duckdb running on PostgreSQL 18.

1 Install pig

curl -fsSL https://repo.pigsty.io/pig | bash

2 Set up repos

pig repo set

3 Install what you need

pig install -y pg18 pg_duckdb vector

Supported: EL 8 / 9 / 10 · Debian 12 / 13 · Ubuntu 22 / 24 / 26 · x86_64 and aarch64 · PostgreSQL 14 - 18

WHY IT EXISTS

Installing an Extension Shouldn't Be a Project

A large share of what Postgres can do lives in extensions — and distribution has always been the roughest part of that ecosystem.

WITHOUT PIG

Everything is on you

Work out where the extension even lives: PGDG, a vendor repo, or just a GitHub tarball
Match the PG major, the distro release, and the CPU architecture by hand
No package for your combination? Install a toolchain, learn pgrx, compile — then own the upgrades
Do it again on the next host, and again after the next PG major upgrade

WITH PIG

It is one command

pig repo set writes one coherent apt / dnf setup: OS + PGDG + Pigsty, mirror-aware
pig install pg_duckdb -v 18 resolves the name, the PG major, the distro, and the arch
Off the support matrix? pig build reproduces the very package Pigsty ships
What lands is a native RPM / DEB: remove pig and your database is untouched

pig is never mandatory: the Pigsty repositories work with plain apt and dnf, and pig never becomes a runtime dependency of your database.

CAPABILITIES

The Catalog, the Repos, the Builds — and Day Two

Four capabilities, from getting an extension installed to keeping the database running.

01 · THE CATALOG

562 Extensions, Already Packaged

No package-name guessing. No version matching

pig ext list duck searches the catalog by name, category, and PG version; pig ext info shows the detail
Extension name or package name, both work: pig install vector equals pgvector
pig ext scan -v 18 reports what is actually installed on this host, and what is missing
The catalog ships inside the binary, and pig ext reload refreshes it on its own

Extensions stop being a build problem and become an install

find-and-install.sh

# search the catalog
pig ext list duck

# install for a given PG major
pig install pg_duckdb -v 18

# what is on this host?
pig ext status -v 18

02 · REPOSITORIES

Repositories, Configured Not Improvised

One command writes a coherent APT / YUM setup

pig repo set lays down the OS, PGDG, and Pigsty repositories in one shot
Region detection picks a reachable mirror; mainland China falls back to repo.pigsty.cc
Add or drop by module: pig repo add pgsql node infra, with pig repo status to inspect
It follows PGDG packaging conventions and coexists with whatever you already have

Repository state stays inspectable and reversible, not a pile of hand-edited .repo files

repo.status

# what pig manages for you
/etc/yum.repos.d/ pigsty-*.repo
/etc/apt/sources.list.d/ pigsty.list
modules: node pgsql infra
region: default | china

03 · BUILD FROM SOURCE

No Package? Build the Same One

The build environment is a command, not a wiki page

pig build tool and rust lay down the toolchain and pgrx without dependency archaeology
pig build spec fetches the very specs Pigsty uses to produce its own packages
The output is a conventional RPM / DEB that drops straight into your own internal repository

A defined path exists even outside the support matrix

PIG // BUILD SURFACEREPRODUCIBLE · PGDG-COMPLIANT RPMel8 · el9 · el10 DEBbookworm · trixie PGRXrust extensions PGXSc extensions SPECbuild recipes REPOlocal package feed SAME SPEC AS THE SHIPPED PACKAGES →

04 · DAY TWO

All the Way to Point-in-Time Recovery

Past the package manager, a well-behaved local toolbox

pig pg wraps local pg_ctl / psql primitives; pig pt forwards to patronictl unchanged
pig pb manages pgBackRest backups; pig pitr orchestrates recovery conservatively — Patroni stays down until you say otherwise
pig inventory edits pigsty.yml losslessly — comments, key order, and anchors survive byte for byte, and invalid YAML never reaches disk
pig sty turns a host into a full Pigsty PostgreSQL RDS

High-risk operations show a plan and ask first; nothing decides on your behalf

pig pitr --plan

# conservative by default
precheck: repo, cluster, pgdata
stop: patroni, then postgres
restore: pgbackrest --target
start: only when asked

# patroni stays down until you say so

COMMAND SURFACE

One CLI for the Whole Lifecycle

Every subcommand has pig help and a documentation page. Consistent flags, stable output.

Command Reference → Installation → Release Notes →

RPrepoAPT / YUM repos EXextExtension catalog INinstallNative package install BDbuildBuild from source PGpostgresLocal PostgreSQL PTpatronipatronictl passthrough PBpgbackrestBackup and restore PIpitrPoint-in-time recovery STstyPigsty control IVinventoryConfig inventory

ONE COMMAND AWAY

Browse all 562 extensions →

AUTOMATION

Written to Be Scripted

The same commands read well in a terminal and parse reliably from a script or an agent.

-o json | yamlSelf-describing output; stdout carries the result only --planPreview destructive steps first; -y for unattended runs Defined exit codesUsage error → 2, missing confirmation → 7; scripts can branch

DOWNLOAD

Get PIG

A one-line install script, or your own package manager. Either way it is the same static binary.

INSTALL SCRIPT

One Line

curl -fsSL https://repo.pigsty.io/pig | bash

The script detects your OS and architecture, fetches the matching RPM / DEB, and hands it to rpm or dpkg.

EL 8/9/10Debian 12/13Ubuntu 22/24/26amd64 · arm64

Read the install guide

PACKAGE OR BINARY

apt / dnf

Add the Pigsty Infra repository, then apt install pig or dnf install pig. Or just take the binary out of the release tarball and drop it on your PATH.

rpmdebtarballmacOS

See the release artifacts

Start with the tutorial Read the source on GitHub