Pigsty

• 1: Pigsty v4.5: 575 Extensions, Kafka, MySQL, Valkey, and Silo
• 2: Pigsty v4.3: 510 Extensions & Ubuntu 26
• 3: Pigsty v4.2: 12 Kernels
• 4: Pigsty v4.1: Day-Zero 18.2 Support
• 5: Pigsty v4.0: Victoria Stack + Security Hardening
• 6: Pigsty v3.7: PostgreSQL Magneto Award, PG18 Deep Support
• 7: Pigsty v3.6: The Ultimate PostgreSQL Distribution
• 8: Pigsty v3.5: 4K Stars, PG18 Beta, 421 Extensions
• 9: Pigsty v3.4: PITR Enhancement, Locale Best Practices, Auto Certificates
• 10: Pigsty v3.3: 404 Extensions, Turnkey Apps, New Website
• 11: Pigsty v3.2: The pig CLI, Full ARM Support, Supabase & Grafana Enhancements
• 12: Pigsty v3.1: One-Click Supabase, PG17 Default, ARM & Ubuntu 24
• 13: Pigsty v3.0: Pluggable Kernels & 340 Extensions
• 14: Pigsty v2.7: The Extension Superpack
• 15: Pigsty v2.6: PostgreSQL Crashes the OLAP Party
• 16: Pigsty v2.5: Ubuntu & PG16
• 17: Pigsty v2.4: Monitor Cloud RDS
• 18: Pigsty v2.3: Richer App Ecosystem
• 19: Pigsty v2.2: Monitoring System Reborn
• 20: Pigsty v2.1: Vector + Full PG Version Support!
• 21: Pigsty v2.0: Open-Source RDS PostgreSQL Alternative
• 22: Pigsty v1.5: Docker Application Support, Infrastructure Self-Monitoring
• 23: Pigsty v1.4: Modular Architecture, MatrixDB Data Warehouse Support
• 24: Pigsty v1.3: Redis Support, PGCAT Overhaul, PGSQL Enhancements
• 25: Pigsty v1.2: PG14 Default, Monitor Existing PG
• 26: Pigsty v1.1: Homepage, Jupyter, Pev2, PgBadger
• 27: Pigsty v1.0: GA Release with Monitoring Overhaul
• 28: Pigsty v0.9: CLI + Logs
• 29: Pigsty v0.8: Service Provisioning
• 30: Pigsty v0.7: Monitor-Only Deployments
• 31: Pigsty v0.6: Provisioning Upgrades
• 32: Pigsty v0.5: Declarative DB Templates
• 33: Pigsty v0.4: PG13 and Better Docs
• 34: Pigsty v0.3: First Public Beta

1 - Pigsty v4.5: 575 Extensions, Kafka, MySQL, Valkey, and Silo

Pigsty v4.5.0 is a feature release spanning data services, the PostgreSQL ecosystem, automation safety, and the software supply chain. It adds Kafka KRaft and MySQL 8.4 pilot modules, adds a Valkey engine to REDIS, converges the MINIO module on Silo, and grows the packaged PostgreSQL extension catalog from 531 to 575.

This full review covers 100 commits, 416 files, 42,058 insertions, and 15,984 deletions from v4.4.0 (2026-07-10) to v4.5.0 (dab5dba3, 2026-08-14). See the complete source diff at v4.4.0...v4.5.0. A substantial share of the structured diff comes from re-exporting the entire Grafana dashboard set to Dashboard API v2.

Release Highlights

• 575 PostgreSQL extensions: 46 entries added and 2 removed, for a net gain of 44. Many Rust extensions move to pgrx 0.19.1, with synchronized RPM/DEB coverage and package-name mappings.
• Kafka KRaft module: Native Kafka orchestration with multi-cluster support, dynamic enrollment and retirement, SCRAM-SHA-512/TLS, credential rotation, health gates, monitoring, alerting, and four Grafana dashboards.
• MySQL 8.4 module: Standalone and three-node InnoDB Cluster deployments with MySQL Router, XtraBackup, account and database provisioning, parameter protection, monitoring, alerting, and conservative retirement workflows.
• Valkey and Silo: REDIS adds redis_type: valkey; MINIO now accepts only minio_type: silo. The RustFS backend developed during this cycle was withdrawn before the final baseline.
• Safer cluster orchestration: PGSQL, REDIS, MINIO, KAFKA, and MYSQL select members by explicit cluster identity. etcd delegation, DBSU key exchange, PITR, backup markers, and removal workflows are tightened as well.
• Observability upgrades: New Kafka and MySQL dashboards, MinIO/Silo Metrics V3, and pg_exporter 1.4-series configuration with PG19, transaction-age, lock, replication, and cleanup-pressure coverage.
• Repository and supply-chain upgrades: SOW now generates local repositories atomically without fabricated ModuleMD. Offline bundles can carry versioned source archives. Infra repackaging standardizes SHA-256-pinned inputs, SPDX licenses, and the 1PGSTY release suffix.
• 51 standalone configuration templates: Adds demo/kafka, demo/mysql, and the eight-node ha/octo simulation, while updating ha/trio to a compact three-node Silo HA topology.

Kafka KRaft Pilot Module

The new Kafka module uses node state as the source of truth and manages brokers and controllers with dynamic KRaft. It supports multiple Kafka clusters in one inventory and unbounded kafka.yml runs; incomplete --limit selections are rejected to avoid updating only part of the quorum.

• Nodes persist authoritative manifests and secrets, supporting dynamic controller joins, broker admission, member retirement, and three-stage failed-member replacement.
• SCRAM-SHA-512, TLS, certificate rotation, and credential rotation are supported, followed by partition-health and protocol self-tests.
• kafka-rm.yml requires a non-empty -l/--limit and validates absolute data paths, target identity, and the surviving anchors needed for partial retirement before stopping services.
• Adds JMX Exporter, Kafka Exporter, Victoria scrape and alert rules, plus Overview, Instance, Topic, and Consumer Grafana dashboards.

Kafka remains a pilot module. Clients must resolve and reach every broker directly; do not put the Kafka data plane behind HAProxy, a VIP, or a conventional L4 load balancer.

MySQL 8.4 Pilot Module

The new MySQL module targets a fixed MySQL 8.4 LTS platform. It supports a standalone instance or a three-node InnoDB Cluster and includes MySQL Shell, MySQL Router, TLS, user/database provisioning, scheduled full XtraBackup backups, and unified monitoring.

• Initialization validates exactly one or three members, creates the cluster, coordinates Router, and handles existing members and partial states idempotently.
• mysql_parameters protects replication, TLS, and platform-reserved settings; loose_, skip_, disable_, and enable_ prefixes cannot bypass the guardrails.
• mysql_databases accepts only name, encoding, and collate; databases are created with DEFAULT ENCRYPTION='N'.
• Removal validates the target, quorum, and member state before isolation, shutdown, and cleanup. Unlike other modules, mysql-rm.yml fails closed when a selected host has no MySQL identity.
• Adds Overview, Cluster, Instance, Replication, and Alert Grafana dashboards plus mysqld_exporter alerts.

Valkey, Silo, and Mongo Mode

Redis / Valkey

REDIS keeps Redis as the default engine and can select Valkey explicitly with redis_type: valkey. Valkey uses the valkey-server and valkey-cli packages, while configuration paths, monitoring jobs, service interfaces, and module parameters retain redis names for compatibility with existing inventories and dashboards.

Redis/Valkey systemd units now use Type=notify with a 1,800-second startup timeout. Topology validation, primary/replica relationships, password handling, tag-scoped removal, and rebuild protection are also strengthened.

MINIO / Silo

MINIO remains the compatibility module name, but the v4.5 role deploys Silo and only Silo; silo is the sole valid minio_type. Silo preserves the S3/Admin APIs, /minio/* routes, MINIO_* environment variables, and existing disk format, while the package, binary, and systemd service are now named silo.

• Startup checks the systemd Invocation ID, ActiveState=active, and Silo cluster health, waiting up to roughly 600 seconds so stale process state is not mistaken for a successful restart.
• Object-storage members are grouped by minio_cluster, independent of the inventory group name. Multi-cluster inventories should use distinct minio_alias, minio_domain, and minio_endpoint values.
• ha/trio changes from single-node object storage to three single-disk Silo members with EC:1, exposed on port 9002 through VIP and HAProxy. The template declares all three default users explicitly so configure -g produces consistent S3 credentials.
• Distributed Silo requires /data/minio to be a separate filesystem; Silo rejects an ordinary directory on the root filesystem.
• A RustFS backend was added during development and fully withdrawn from the final source. Infra repositories may still carry RustFS or MinIO packages, but neither is a supported v4.5 MINIO backend.

PostgreSQL Mongo Mode

The standalone FERRET role and mongo.yml playbook are removed. Their function is split between PostgreSQL Mongo mode and the FerretDB Docker APP: PostgreSQL/DocumentDB provides the data layer, and FerretDB in Docker Compose provides the MongoDB protocol layer. Pigsty no longer ships the old FerretDB systemd service, dedicated scrape configuration, or Mongo dashboards.

Orchestration, Security, and Lifecycle

• deploy.yml, slim.yml, and the PGSQL, REDIS, MINIO, KAFKA, and MYSQL initialization playbooks skip unrelated hosts by their respective *_cluster identities. PGSQL, REDIS, MINIO, and KAFKA removal playbooks apply the same rule.
• PGSQL configuration, PITR, and removal delegate only when a canonical, non-empty etcd group exists. DBSU SSH keys are exchanged among actual pg_cluster_members, including cross-inventory-group topologies such as Citus.
• PITR and removal delete only etcd subtrees bounded by /<cluster>/, avoiding accidental deletion when one cluster name prefixes another. The initial pgBackRest backup writes initial.done only after the command succeeds.
• Removal workflows stop services before cleaning data. Kafka, MySQL, and object storage add directory, quorum, surviving-member, and cluster-identity checks.
• A full pgsql.yml run is now explicitly described as initialization-only: it restarts Patroni/PostgreSQL and reapplies managed configuration and bootstrap SQL, so it is not a routine convergence command for initialized clusters.
• Pigsty-rendered systemd units live under /etc/systemd/system; permissions are tightened for sensitive configuration, environment files, keys, and privileged scripts. Debian/Ubuntu package installation suppresses premature starts of Silo, Redis/Valkey, and legacy logging services.
• HAProxy uses a fixed /etc/haproxy/haproxy.cfg plus /etc/haproxy/conf.d layout, upstream master-worker mode, a master socket, and Type=notify. dnsmasq uses dynamic binding, answers private PTR locally, and handles node addresses that appear only after INFRA initialization.
• Debian/Ubuntu time sync writes the native /etc/chrony/chrony.conf, while EL continues to use /etc/chrony.conf. During initial synchronization, offsets greater than ten seconds may step within the first 120 updates.

PostgreSQL Kernels and Extensions

• Default PostgreSQL updates to 18.6 with the repositories. The four standard Patroni templates add an output_plugin_libraries allowlist for pgoutput, test_decoding, and wal2json; Patroni filters unsupported settings on older versions.
• The PostgreSQL 19 beta template gains pgBackRest 2.59 and scheduled backup support. It still installs no extensions by default and remains a PG19 trial template.
• Percona PostgreSQL 18 TDE uses cluster mode and keeps Pigsty’s private installation prefix to avoid collisions with native PostgreSQL.
• IvorySQL gains default-database initialization and compatible WAL compression in the standard workload templates.
• The PostgreSQL fact loader, per-platform package_map, and default extension groups are refreshed together, fixing PGDG/YUM names and missing packages.

Comparing the embedded catalog snapshots in Pig v1.5.1 (531 entries) and v1.7.0 (575 entries), this cycle adds 46 extensions and removes 2, for a net gain of 44:

• 32 primary extensions added: argm, cat_tools, cron_utils, fbsql, oidc_validator, online_advisor, pg_cjk_parser, pg_column_tetris, pg_describe, pg_disorder, pg_fts, pg_jieba, pg_kpart, pg_lake, pg_local_cache, pg_mentat, pg_oidc_validator, pg_policy, pg_roast, pg_tiktoken_c, pg_turbovec, pg_vault_tde, pgcontext, pgfr_record, pgmemento, pgmonitor, pgsqlmock, pgwasm, plruby, plx, postbis, and qdgc.
• 13 subextensions added: hstore_plruby, jsonb_plruby, ltree_plruby, pg_extension_base, pg_extension_updater, pg_lake_copy, pg_lake_engine, pg_lake_iceberg, pg_lake_table, pg_map, pgcontext_pgvector, pgfr_analyze, and qdgc_postgis.
• One PGDG extension added: pg_statviz. It remains in the online catalog but is not part of the default installation groups.
• pg_analytics and spat removed: the former is archived, and the latter is a deprecated alpha project.

In addition, emailaddr, explain_ui, the Rust oidc_validator, pg_summarize, and smlar leave the default installation groups because upstream does not provide a distributable license; packages and catalog records may remain. pg_relation_sql is a standalone SQL toolkit without CREATE EXTENSION support, so it appears in the packaging table but is not counted among the 575 extensions.

Extension Package Update Matrix

The table consolidates RPM and DEB batches after v4.4.0 into one final “old version → final version” row per extension: 207 packaged entries plus two catalog removals. Where RPM and DEB differ, both are shown. An unchanged version can still represent a rebuild or a change in package naming, license metadata, or platform coverage.

The first packaging log after July 10 covers July 7–24 without per-entry dates, so the whole batch is included to avoid omitting post-release pgrx 0.19.1 rebuilds and matrix fixes. The final repository indexes remain authoritative for versions and platform availability.

Observability

• The complete Grafana dashboard set is re-exported through the Pig/Grafana tooling as Dashboard API v2. Four Kafka and five MySQL dashboards are added, and links, variables, and layouts are refreshed for Node, PostgreSQL, Redis, and Infra dashboards.
• MinIO/Silo Overview and Instance dashboards move to Metrics V3. Victoria scrapes /minio/metrics/v3 and drops high-cardinality samples with a non-empty bucket label.
• pg_exporter configuration updates to 1.4.0 and fixes the duplicate time series produced by the 1.4.1 pg_subrel query.
• PG19 gains pg_sub_19, pg_recovery_state, pg_wal_19, pg_lock_stat, and pg_vacuum_score collectors. PG10+ gains a pg_xact_age transaction-age histogram, replication-slot idle_timeout, and WAL Receiver connecting state encoding.
• Kafka JMX/protocol exporters and the MySQL exporter join unified service discovery, Victoria scraping, and alert rules. Journald records without a PRIORITY field are handled safely.

Repositories, Offline Bundles, and Supply Chain

• REPO and CACHE use sow create --pigsty to generate DNF/APT metadata and the SHA-256 repo_complete marker atomically, without injecting fabricated ModuleMD.
• module_hotfixes becomes an explicit per-repository choice and is enabled only for EL repositories that must replace system module streams, avoiding indiscriminate DNF module-filter bypasses.
• If dist/<version>/pigsty-<version>.tgz already exists, cache.yml includes it in the offline repository. It does not implicitly package the current worktree or download source code from the internet.
• RPM exporter package names change from underscores to hyphens, for example node_exporter → node-exporter; unversioned Provides/Obsoletes entries bridge the old names.
• Local Infra repackaging standardizes the PGSTY vendor, SPDX license expressions, 1PGSTY release suffix, /etc/default/<service> environment files, vendor units under /usr/lib/systemd/system, and legal files under /usr/share/doc/<package>.
• Simple binary packages use reproducible upstream archives pinned by SHA-256; vendor-native RPM/DEB files retain their original bytes and metadata. Direct artifacts such as Silo, Grafana, Code, Code Server, and Vector gain pinned URLs and checksums.
• China-region routing is refreshed systematically: operating systems, Docker, Grafana, Percona, MongoDB APT, and uv/PyPI prefer Tencent Cloud; EL/Docker retain Huawei Cloud and Alibaba Cloud fallbacks; MySQL/Kubernetes use USTC; ClickHouse uses Huawei Cloud.

Infra Package Update Matrix

The table consolidates this cycle’s Infra batches into one row per package, showing only the v4.4.0 value, final v4.5.0 value, and essential notes. Intermediate versions are omitted. “Built” or “verified” describes packaging records only; the signed repository index at release time remains authoritative for installable versions.

Platforms, Templates, and Release Engineering

• Recommended platform baselines update to Rocky Linux 9.8/10.2, Debian 12.15/13.6, and Ubuntu 22.04.5/24.04.4/26.04.0. Terraform cloud images and pinned Vagrant box versions are refreshed with them.
• Vagrant’s root disk becomes configurable through root_disk: 64 GiB by default and 128 GiB for the all, rpm, deb, oss, and pro build matrices. The existing disk setting still means the extra /data disk and defaults to 128 GiB. The vagrant user’s login shell is standardized on Bash.
• Adds the eight-node ha/octo simulation. ha/trio becomes a three-node Silo deployment behind VIP/HAProxy; demo/minio explicitly selects Silo and narrows its local repository package groups.
• The safe and demo templates use valid extension aliases. Tuned-profile paths adapt to the operating system, cluster-size comparisons remain compatible with Ansible versions before 2.19, and unused internal flags plus MINIO/INFRA variables are removed.
• The Docker base image updates to Debian 13.6 and is marked v4.5.0. Image publishing becomes manually triggered and builds from tags.
• docker/Makefile fixes its data directory at repository-local ./data; make purge no longer accepts an external DATA override and has no countdown.
• GitHub Actions updates checkout, CodeQL, Docker build/login, and Cosign in bulk. Release, bootstrap, installation, checksum, and build templates tighten parameter and file handling.
• Release archives generate top-level pigsty.yml from conf/meta.yml, include Kafka/MySQL playbooks, and remove the old Mongo playbook. The signing workflow creates Cosign signatures only for the pigsty-<tag>.tgz source archive, not multi-gigabyte offline bundles.
• README, SECURITY, CONTRIBUTING, AGENTS, and NOTICE align on v4.5, 575 extensions, Silo, Redis/Valkey, and Mongo mode, with updated 2026 copyright and trademark language.

Compatibility Changes and Upgrade Notes

Before upgrading from v4.4, review these changes carefully:

1. FERRET split: Remove the old ferretdb systemd service. Deploy the DocumentDB data layer through Mongo configuration mode, then deploy the FerretDB protocol layer with docker.yml / app.yml. The old mongo.yml, mongo_* parameters, and dedicated dashboards are gone.
2. Silo replaces the MinIO server: minio_type accepts only silo. Protocol and disk-format compatibility do not constitute migration acceptance; validate backups, in-place compatibility, rollback, and real read/write traffic before switching existing object storage.
3. ha/trio object-storage topology changes: The new template uses three single-disk Silo members. Do not expand an existing single-node pool in place by simply adding two members; create a new cluster and migrate objects.
4. HAProxy unit changes: Pigsty no longer renders /etc/default/haproxy, though the unit can read it when present. Use EXTRAOPTS only, keep -S /run/haproxy-master.sock, and do not add -f.
5. Explicit cluster identity: Custom inventories must define pg_cluster, redis_cluster, minio_cluster, kafka_cluster, or mysql_cluster for target hosts. Older inventories that relied only on fixed group names must add these identities.
6. Full PGSQL playbook is initialization-only: Do not run the complete pgsql.yml against initialized nodes. Use precise tags for routine maintenance; for a full rebuild, validate backups and remove the target member through the formal workflow first.
7. Valkey is opt-in: Valkey is installed only with redis_type: valkey; module parameters, configuration paths, and monitoring interfaces keep Redis names.
8. SOW is a core dependency: REPO/CACHE requires SOW 0.3.0. If an old offline bundle or local repository lacks sow, add it from the Pigsty Infra repository first.
9. Exporter RPM renames: External automation and private repositories should move from old names such as node_exporter and redis_exporter to node-exporter and redis-exporter.
10. Default extension groups tighten licensing: Environments that depend on emailaddr, explain_ui, oidc_validator, pg_summarize, or smlar must install them explicitly and assess licensing and redistribution boundaries independently.
11. Docker purge semantics change: make purge directly deletes repository-local ./data; confirm that it contains no container data you need to retain.
12. Vagrant disk semantics change: root_disk controls the system disk, while disk controls the extra /data disk. Distributed Silo requires the latter to be a real independent mount.

Get v4.5.0

Install on a fresh, supported Linux node:

curl -fsSL https://repo.pigsty.io/get | bash -s v4.5.0
cd ~/pigsty
./bootstrap
./configure
./install.yml

A production upgrade is not an overwrite installation. Read the compatibility changes above, resolve the exact target cluster, backup, inventory identity, and live state, then use an explicit -l scope for check mode or maintenance operations.

2 - Pigsty v4.3: 510 Extensions & Ubuntu 26

Pigsty v4.3 adds 50 PostgreSQL extensions, bringing the total to 510. It also adds Ubuntu 26.04 x86_64/arm64 support, refreshes Supabase, pgEdge, PolarDB, Grafana, MinIO, and a batch of infra packages. Read more

3 - Pigsty v4.2: 12 Kernels

GitHub Release | Release Note

v4.2.0 Release Note

Highlights

• Aligned with PostgreSQL out-of-band minor updates: 18.3, 17.9, 16.13, 15.17, 14.22.
• Total PostgreSQL extension coverage reaches 461 packages.
• Kernel updates across Babelfish, AgensGraph, pgEdge, OriolePG, OpenHalo, and Cloudberry.
• Babelfish template now uses a Pigsty-maintained PG17-compatible build, with no WiltonDB repo dependency.
• Supabase images and self-hosted templates are refreshed to the latest stack, using Pigsty-maintained pgsty/minio.

Major Changes

• mssql now defaults to Babelfish PG17 (pg_version: 17, pg_packages: [babelfish, pgsql-common, sqlcmd]) and no longer requires an extra mssql repo.
• Kernel install paths are normalized in pg_home_map: mssql -> /usr/babelfish-$v/, gpsql -> /usr/local/cloudberry.
• package_map adds a dedicated cloudberry mapping and fixes babelfish* aliases to versioned RPM/DEB package names.
• Redis data root default changes from /data to /data/redis; deployment blocks legacy defaults, while redis_remove keeps backward-compatible cleanup.
• configure now supports absolute -o output paths with auto-created parent directories, tri-state region detection (CN/global/offline fallback), and a fix for behind_gfw() hangs.
• Debian/Ubuntu default repo URL mappings (updates/backports/security) and China mirror components are corrected to prevent bootstrap package failures.
• Supabase stack is updated (including PostgREST 14.5 and Vector 0.53.0) and now includes missing S3 protocol credential variables.
• Rich/Sample templates explicitly define dbuser_meta defaults; node.sh systemd completion is simplified.
• pgbackrest stanza initialization now retries (2 attempts, 5-second interval) to reduce lock contention with archive-push.
• Vibe template now ships @anthropic-ai/claude-code, @openai/codex, and happy-coder, and includes age in the default example.

PG Software Updates

• PostgreSQL 18.3, 17.9, 16.13, 15.17, 14.22
• RPM Changelog 2026-02-27
• DEB Changelog 2026-02-27
• Core upgrades: timescaledb 2.25.0 -> 2.25.1, citus 14.0.0-3 -> 14.0.0-4, pg_search -> 0.21.9
• New/rebuilt: pgedge 17.9, spock 5.0.5, lolor 1.2.2, snowflake 2.4, babelfish 5.5.0, cloudberry 2.0.0
• Kernel-side updates: oriolepg 17.11 -> 17.16, orioledb beta12 -> beta14, openhalo 14.10 -> 1.0(14.18)

Infrastructure Software Updates

API Changes

• pg_mode now includes agens and pgedge.
• mssql defaults are updated to pg_version: 17 and pg_packages: [babelfish, pgsql-common, sqlcmd].
• Kernel/package alias mappings are updated in pg_home_map and package_map (Babelfish, OpenHalo, IvorySQL, Cloudberry, pgEdge family).
• redis_fs_main now defaults to /data/redis, with deployment guardrails and backward-compatible cleanup behavior.
• configure output path handling and region detection logic are updated, with offline fallback warnings and unified SSH probe timeouts.
• grafana.ini.j2 is updated for Grafana 12.4 config changes and deprecations.

Compatibility Notes

• If existing Redis configs still use redis_fs_main: /data, migrate to /data/redis before deployment.
• Grafana 12.4 changes data link merge behavior. This release moves key links into field overrides; review custom dashboards accordingly.

26 commits, 122 files changed, +2,116 / -2,215 lines (v4.1.0..v4.2.0, 2026-02-15 ~ 2026-02-28)

Checksums

24a90427a7e7351ca1a43a7d53289970  pigsty-v4.2.0.tgz
d980edf5eeb0419d4f1aa7feb0100e14  pigsty-pkg-v4.2.0.d12.aarch64.tgz
24bc237d841457fbdcc899e1d0a3f87e  pigsty-pkg-v4.2.0.d12.x86_64.tgz
e395b38685e2ecbe9c3a2850876d9b7b  pigsty-pkg-v4.2.0.d13.aarch64.tgz
c5c8776f9bead9f29528b26058801f83  pigsty-pkg-v4.2.0.d13.x86_64.tgz
28ea40434bd06135fc8adc0df1c8407d  pigsty-pkg-v4.2.0.el10.aarch64.tgz
58ad715ac20dc1717d1687daecfcf625  pigsty-pkg-v4.2.0.el10.x86_64.tgz
008f955439ea311581dd0ebcf5b8bd34  pigsty-pkg-v4.2.0.el8.aarch64.tgz
2acfd127a517b09f07540f808fe9547a  pigsty-pkg-v4.2.0.el8.x86_64.tgz
58e62a92f35291a40e3f05839a1b6bc4  pigsty-pkg-v4.2.0.el9.aarch64.tgz
d311bfdf5d5f60df5fe6cb3d4ced4f9c  pigsty-pkg-v4.2.0.el9.x86_64.tgz
c98972fe9226657ac1faa7b72a22498b  pigsty-pkg-v4.2.0.u22.aarch64.tgz
44a174ee9ba030ac1ea386cf0b85f6e7  pigsty-pkg-v4.2.0.u22.x86_64.tgz
143e404f4681c7d0bbd78ef7982cd652  pigsty-pkg-v4.2.0.u24.aarch64.tgz
00dfa86f477f3adff984906211ab3190  pigsty-pkg-v4.2.0.u24.x86_64.tgz

4 - Pigsty v4.1: Day-Zero 18.2 Support

Same-day production support for new PG minors is the core message of Pigsty v4.1. Read more

5 - Pigsty v4.0: Victoria Stack + Security Hardening

VictoriaMetrics/Logs replace Prometheus/Loki for 10x observability performance, Vector handles logs, unified UI, firewall/SELinux/credential hardening. Read more

6 - Pigsty v3.7: PostgreSQL Magneto Award, PG18 Deep Support

PostgreSQL 18 becomes the default version, EL10 and Debian 13 support added, extensions reach 437, and Pigsty wins the PostgreSQL Magneto Award. Read more

7 - Pigsty v3.6: The Ultimate PostgreSQL Distribution

New doc site, PITR playbook, Percona PG TDE kernel support, and Supabase self-hosting optimization make v3.6 the last major release before 4.0. Read more

8 - Pigsty v3.5: 4K Stars, PG18 Beta, 421 Extensions

Pigsty crosses 4K GitHub stars, adds PG18 beta support, pushes extensions to 421, ships new doc site, and completes OrioleDB/OpenHalo full-platform support. Read more

9 - Pigsty v3.4: PITR Enhancement, Locale Best Practices, Auto Certificates

Pigsty v3.4 adds pgBackRest backup monitoring, cross-cluster PITR restore, automated HTTPS certificates, locale best practices, and full-platform IvorySQL and Apache AGE support. Read more

10 - Pigsty v3.3: 404 Extensions, Turnkey Apps, New Website

Pigsty v3.3 pushes available extensions to 404, adds turnkey app deployment with app.yml, delivers Certbot integration for automated HTTPS, and launches a redesigned website. Read more

11 - Pigsty v3.2: The pig CLI, Full ARM Support, Supabase & Grafana Enhancements

Pigsty v3.2 introduces the pig CLI for PostgreSQL package management, complete ARM64 extension repository support, and Supabase & Grafana enhancements. Read more

12 - Pigsty v3.1: One-Click Supabase, PG17 Default, ARM & Ubuntu 24

Pigsty v3.1 makes PostgreSQL 17 the default, delivers one-click Supabase self-hosting, adds ARM64 and Ubuntu 24.04 support, and simplifies configuration management. Read more

13 - Pigsty v3.0: Pluggable Kernels & 340 Extensions

Pigsty v3.0 ships 340 extensions across EL/Deb with full parity, adds pluggable kernels (Babelfish, IvorySQL, PolarDB) for MSSQL/Oracle compatibility, and delivers a local-first state-of-the-art RDS experience. Read more

14 - Pigsty v2.7: The Extension Superpack

Pigsty v2.7 bundles 255 PostgreSQL extensions, plus Docker templates for Odoo, Supabase, PolarDB, and Jupyter, with new PITR dashboards. Read more

15 - Pigsty v2.6: PostgreSQL Crashes the OLAP Party

Pigsty v2.6 makes PostgreSQL 16.2 the default, introduces ParadeDB and DuckDB support, and brings epic-level OLAP improvements. Read more

16 - Pigsty v2.5: Ubuntu & PG16

Pigsty v2.5 adds Ubuntu/Debian support (bullseye, bookworm, jammy, focal), new extensions including pointcloud and imgsmlr, and redesigned monitoring dashboards. Read more

17 - Pigsty v2.4: Monitor Cloud RDS

Pigsty v2.4 delivers PostgreSQL 16 GA support, RDS/PolarDB monitoring, Redis Sentinel HA, and a wave of new extensions including Apache AGE, zhparser, and pg_embedding. Read more

18 - Pigsty v2.3: Richer App Ecosystem

Pigsty v2.3 adds FerretDB MongoDB support, NocoDB integration, L2 VIP for node clusters, PostgreSQL security patches, and Redis 7.2. Read more

19 - Pigsty v2.2: Monitoring System Reborn

Pigsty v2.2 delivers a complete monitoring dashboard overhaul built on Grafana 10, a 42-node production simulation sandbox, Pigsty’s own RPM repos, and UOS compatibility. Read more

20 - Pigsty v2.1: Vector + Full PG Version Support!

Pigsty v2.1 provides support for PostgreSQL 12 through 16, with PGVector for AI embeddings. Read more

21 - Pigsty v2.0: Open-Source RDS PostgreSQL Alternative

Pigsty v2.0 delivers major improvements in security, compatibility, and feature integration — truly becoming a local open-source RDS alternative. Read more

22 - Pigsty v1.5: Docker Application Support, Infrastructure Self-Monitoring

Complete Docker support, infrastructure self-monitoring, ETCD as DCS, better cold backup support, and CMDB improvements. Read more

23 - Pigsty v1.4: Modular Architecture, MatrixDB Data Warehouse Support

Pigsty v1.4 introduces a modular architecture with four independent modules, adds MatrixDB time-series data warehouse support, and delivers global CDN acceleration. Read more

24 - Pigsty v1.3: Redis Support, PGCAT Overhaul, PGSQL Enhancements

Pigsty v1.3 adds Redis support with three deployment modes, rebuilds the PGCAT catalog explorer, and enhances PGSQL monitoring dashboards. Read more

25 - Pigsty v1.2: PG14 Default, Monitor Existing PG

Pigsty v1.2 makes PostgreSQL 14 the default version and adds support for monitoring existing database instances independently. Read more

26 - Pigsty v1.1: Homepage, Jupyter, Pev2, PgBadger

Pigsty v1.1.0 ships with a redesigned homepage, plus JupyterLab, PGWeb, Pev2 & PgBadger integrations. Read more

27 - Pigsty v1.0: GA Release with Monitoring Overhaul

Pigsty v1.0.0 GA is here — a batteries-included, open-source PostgreSQL distribution ready for production. Read more

28 - Pigsty v0.9: CLI + Logs

One-click installs, a beta CLI, and Loki-based logging make Pigsty easier to land. Read more

29 - Pigsty v0.8: Service Provisioning

Services are now first-class objects, so you can define any routing policy—built-in HAProxy, L4 VIPs, or your own balancer. Read more

30 - Pigsty v0.7: Monitor-Only Deployments

Monitor-only deployments unlock hybrid fleets, while DB/user provisioning APIs get a serious cleanup. Read more

31 - Pigsty v0.6: Provisioning Upgrades

v0.6 reworks the provisioning flow, adds exporter toggles, and makes the monitoring stack portable across environments. Read more

32 - Pigsty v0.5: Declarative DB Templates

Pigsty v0.5 introduces declarative database templates so roles, schemas, extensions, and ACLs can be described entirely in YAML. Read more

33 - Pigsty v0.4: PG13 and Better Docs

Pigsty v0.4 ships PG13 support, a Grafana 7.3 refresh, and a cleaned-up docs site for the second public beta. Read more

34 - Pigsty v0.3: First Public Beta

Pigsty v0.3.0, the first public beta, lands with eight battle-tested dashboards and an offline bundle. Read more