Supported version of postgresql

Products

• CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

We are planning to upgrade our environment from DX APM 10.7 H84 to DX APM 10.8.

Before proceeding, we would like to confirm the supported PostgreSQL versions for DX APM 10.8.

Is PostgreSQL 13.4 mandatory/recommended, or are newer versions such as PostgreSQL 16 or PostgreSQL 17 also officially supported and certified?

If PostgreSQL 16 or 17 are supported, could you please provide the corresponding compatibility matrix or documentation?

Resolution

So in 10.8, PostgreSQL installation is not part of the 10.8 installation and must be installed before you start the 10.8 installation.  What it does is it upgrades the schema only.

So you need to upgrade from 9.6.2 to 14.x first.  The APM installer will upgrade the schema alone.

Upgrade the PostgreSQL Database

10.8 supported 13.x when it first came out.  Let me discuss internally if you can go from 9.6.2 to 17.x and then upgrade to 10.8.

The process is to upgrade the EM first and then upgrade Postgres to latest version if needed. So it has to be 10.7 HF84 -> 10.8 GA -> to latest 10.8 version. The 10.8 GA is a must in this process. If the Postgres is already upgraded to higher version, there is no limitation in upgrading to 10.8
 
in other words it doesn't matter what postgres from the above mentioned they have, they can do the upgrade of EM. Critical piece is the 10.8GA version of EM. Postgres can be upgraded after to whatever version they want, there is no limitation from our side.

What we have found on the Windows side was

adminpack was removed from PostgreSQL core in version 14, so PostgreSQL 17 ships no adminpack.dll while PostgreSQL 9.6 and PostgreSQL 13 still have it.

Because the old cluster postgres database had the extension installed, pg_upgrade to PostgreSQL 17 aborts at "Checking for presence of required libraries" (its functions reference the now-missing $libdir/adminpack), whereas PostgreSQL 9.6 to PostgreSQL 13 passes untouched.

Fix for the direct-to-17 path: run DROP EXTENSION IF EXISTS adminpack; before upgrading.