Apache AGE extension for VMware PostgreSQL 16.x (including 16.6 and later)

Products

VMware Tanzu Data Suite VMware Tanzu for Postgres

Issue/Introduction

Customers running VMware PostgreSQL 16.x (including 16.6 and later) want to know where to obtain the Apache AGE extension to add graph database capabilities when it is not bundled with their Broadcom‑packaged PostgreSQL or Greenplum deployment.

Environment

PostgreSQL 16.x (for example, 16.6, 16.7, 16.8, and later minor releases in the 16 series)
Broadcom‑packaged PostgreSQL or Greenplum Database, where Apache AGE is not included by default
Apache AGE (A Graph Extension) for PostgreSQL 16.x

Cause

Apache AGE is an open‑source graph database extension that is delivered separately from the core PostgreSQL server and is not part of standard PostgreSQL distributions.
Broadcom does not currently bundle or officially support Apache AGE with Greenplum or Broadcom‑distributed PostgreSQL 16.x builds, so there is no Broadcom‑provided binary or product support for this extension at present.

Resolution

Currently, Apache AGE is not bundled or officially supported with Greenplum or Broadcom‑packaged PostgreSQL 16.x, including versions above 16.6.0.

In future releases, Broadcom may choose to bundle or support Apache AGE with Greenplum or Broadcom‑packaged PostgreSQL 16.x; any such change will be documented in product release notes and updated in this article. Customers should subscribe to this KB article for updates.

Workaround

Customers who want to use Apache AGE with PostgreSQL 16.x today can use one of the following approaches, subject to their own testing and support policies.

Option 1: Compile Apache AGE from source

Download the Apache AGE source release that targets PostgreSQL 16 (for example, the 1.5.0 family) from the official Apache AGE downloads page.
Build the extension from source against the exact PostgreSQL 16.x server you run (such as 16.6, 16.7, or 16.8), install it into the server’s extension directory, and then create it in the target database with CREATE EXTENSION age.

Option 2: Use OS / PGDG binary packages

Some package repositories (such as PGDG) provide binary packages like postgresql-16-age that deliver Apache AGE for PostgreSQL 16.
Where available (for example, Ubuntu Jammy PGDG), you can install the postgresql-16-age package alongside an existing PostgreSQL 16 server, ensuring the PostgreSQL server and AGE package come from the same repository/channel so ABI compatibility is maintained.

Option 3: Use Apache AGE with EDB PostgreSQL distributions

EDB documents Apache AGE as a supported extension for PostgreSQL 14–16 in its own Postgres distributions, including EDB Postgres Advanced/Extended Server.
EDB provides installation flows that align with its builds; these apply when running EDB distributions and do not imply support when using Broadcom‑packaged PostgreSQL or Greenplum.

General guidance for “Postgres above 16.6.0.”

For any PostgreSQL 16.x minor version above 16.6, compile Apache AGE from source against that specific PostgreSQL 16.x build when a matching binary package is not available.
If your OS or PGDG channel ships a postgresql-16-age package compatible with your exact PostgreSQL 16.x build, you can use that binary package instead of compiling from source, subject to your organization’s policies.

Additional Information

Important support note

Using Apache AGE with Broadcom products (for example, Greenplum or Broadcom‑packaged PostgreSQL) is currently a customer‑managed customization and is not covered by Broadcom support unless it is explicitly added to the supported‑extension list in future documentation.
Customers should validate Apache AGE with their Broadcom‑packaged PostgreSQL or Greenplum deployments in non‑production environments and follow internal support, change‑management, and compliance processes before deploying to production.

References