HeroDevs
Visit NES for PostgreSQL Home Page

NES for PostgreSQL 14 Source

The source distribution for NES for PostgreSQL 14, a separate product for customers who rebuild from source.

The source distribution for NES for PostgreSQL 14 is a separate product. It is not included with the standard or minimal binary builds, and it requires its own access. Not all subscriptions include source.

Use the source distribution to rebuild NES for PostgreSQL 14 (standard or minimal) and NES for pgpool-II from source on your own infrastructure. It ships the same vendored OpenSSL FIPS provider source, so building from source produces bit-identical FIPS provider artifacts.

Access

The source distribution is a separate product with its own entitlement. If your subscription does not include source access, contact support@herodevs.com or your HeroDevs Account Executive. For more information see Access Tokens.

Contents

The source distribution ships as two artifacts per platform, matching the binary packages:

  • PostgreSQL 14 server source — nes-pg14-postgres-source-<platform>-14.23.tar.gz (Windows ships a .zip)
  • pgpool-II source — nes-pg14-pgpool-source-<platform>-4.5.12.tar.gz (pgpool-II is not built on Windows, so there is no Windows pgpool-II source)

The minimal-profile source artifacts carry a -minimal- infix in the filename (for example, nes-pg14-postgres-source-minimal-linux-14.23.tar.gz).

Each artifact contains:

  • The component source (PostgreSQL 14 or pgpool-II) with NES patches
  • The vendored OpenSSL FIPS provider source, so building from source produces bit-identical FIPS provider artifacts
  • The build scripts and provenance verification scripts
  • Per-platform build instructions (Linux, AIX, Solaris, and Windows for PostgreSQL; Linux, AIX, and Solaris for pgpool-II)

Building

Per-platform build instructions ship with the source distribution, along with the build scripts and the provenance verification scripts. The verification scripts check the vendored source against pinned SHA-256 checksums and GPG signatures before building, and generate a software bill of materials (SBOM). The instructions cover the build flags, toolchain prerequisites, and verification steps for each supported platform.