The Pigsty project has released v3.4, delivering major enhancements for PostgreSQL users who want flexibility, observability, and simplicity in managing self-hosted PG RDS.

The v3.4 introduction Blog. Check more at pigsty.io

The highlight of this release is support for using openHalo, a PostgreSQL 14-based fork that also speaks the MySQL wire protocol on port 3306, allowing seamless migration from MySQL with zero client-side changes. Just install with ./configure -c mysql and connect using either MySQL or PostgreSQL tools.

PostgreSQL’s extensibility is exemplified by 405 extensions, plus its ability to mimic other databases: you can now emulate SQL Server, Oracle, MongoDB, and MySQL on PostgreSQL, and out-of-the-box as RDS service with the help of Pigsty.

Backup and recovery got a major upgrade as well. Pigsty now supports cross-cluster PITR from a centralized repo, with automated restore commands and pgBackRest configs. A new pgbackrest_exporter adds historical backup monitoring so you always know what’s going on.

For app self-hosters, v3.4 simplifies free SSL certificate management with one-click Let’s Encrypt integration. Pigsty automates Certbot certificate issuance through Nginx config—ideal for Supabase, Odoo, and Dify deployments on top of PostgreSQL.

Locale defaults are hardened to use C or C.UTF-8, leveraging PG17’s built-in locale provider where possible. There’s also improved support for Oracle-compatible IvorySQL across all platforms, extended coverage for Apache AGE, and new packages for JuiceFS, Restic, and TimescaleDB EventStreamer.

Pigsty is a full-stack Postgres distribution with 400+ integrated extensions, built as a local-first, battery-included FOSS RDS. Learn more at pigsty.io.

GitHub Release v3.4.1 / v3.4.0