The PostgreSQL Extension Network (PGXN) announced on November 16, 2026 a set of three new GitHub Actions for building, testing and releasing PostgreSQL extensions. PGXN founder David E. Wheeler wrote them over the past few months as a replacement for pgxn/pgxn-tools, the Docker image that many extension authors have used in CI for years.
According to the announcement, the old image had grown large and needed too much upkeep. The new actions are lighter, run faster, and work on every operating system and CPU architecture that GitHub-hosted runners offer, which lets extension authors test on macOS and ARM machines, not only on Linux containers.
What Was Released
Each action handles one part of an extension's workflow:
- pgxn/postgres-action installs a chosen major version of PostgreSQL directly on the runner and starts a server, with no container involved.
- pgxn/matrix-action produces a test matrix of PostgreSQL versions, operating systems and architectures for a workflow to fan out over.
- pgxn/release-action packages a repository and uploads it as a new release on PGXN.
All three are currently tagged at major version v0. Wheeler says he has already used them on several extensions, including semver, pg_clickhouse, chdb and hostname.
How the Actions Work
The release action builds the distribution bundle with git archive, so files can be left out of the upload through a gitattributes file. A dry-run input lets a workflow run on every push but only publish when a version tag is pushed.
The action also returns the archive name, which can then be attached to a GitHub release in a later step.
The matrix action takes inputs such as a minimum and maximum PostgreSQL version, whether to include beta or deprecated releases, and operating systems to exclude. Its list of possible configurations is refreshed by a daily job.
In practice, a project that does not set an upper version will begin testing against the next PostgreSQL major release within a day of its first beta.
The postgres action covers a wide range. Its documentation lists PostgreSQL 8.2 to 19 on Ubuntu runners through the PGDG packages, 14 to 18 on macOS through Homebrew, and 10 to 18 on Windows through Chocolatey. It also installs the pgxn command line client, and on Windows it adds sudo so the same build commands work on every platform.
For extensions that must be loaded through shared_preload_libraries, the action can install PostgreSQL without starting it. The workflow then compiles and installs the module and calls the action a second time with extra server settings appended to postgresql.conf.
Known Gaps
Windows support is not finished. SQL-only extensions pass on Windows with PostgreSQL 17 and 18, but older versions hit a path problem and C extensions do not work at all yet. Wheeler is asking for help from anyone who knows the EDB Windows builds that Chocolatey installs.
He also plans a separate action for pgrx, the Rust framework for writing PostgreSQL extensions, likely within the next few months.
What It Means for Developers
Anyone maintaining a PostgreSQL extension on GitHub gets a simpler path to broad test coverage. Running directly on the runner removes the pull time of a large image and makes it practical to test macOS and ARM builds next to Linux. On Linux, remember that make install needs sudo, because the runner user does not own the PostgreSQL installation.
The daily matrix refresh is the most useful part for long-lived projects. Breakage from a new major release shows up during the beta period instead of after users upgrade. Pair that with the steady stream of minor releases, such as the recent PostgreSQL 18.7 security update, and extensions stay tested against what people actually run.
Teams still on pgxn-tools do not need to switch overnight, but new projects should start with these actions. If your workflows run on older hosted runner types, also check the upcoming GitHub Actions ARM32 retirement.
How to Get Started
Add a matrix job that calls pgxn/matrix-action, feed its output into a build job, and start PostgreSQL in each cell with pgxn/postgres-action before running the usual PGXS build and installcheck steps. For releases, store your PGXN username and password as repository secrets and add pgxn/release-action with dry-run enabled for any push that is not a version tag.
Conclusion
The three new PGXN actions trade one heavy Docker image for small, focused building blocks that cover Linux, macOS and Windows runners. Windows C extensions and pgrx support remain open items, but for most extension authors the new setup is ready to use now.
Sources
- PGXN Blog: Build, Test and Release Extensions with the New PGXN GitHub Actions
- GitHub: pgxn/postgres-action README
See my articles more often when you search Google.
