Re: Update pg_stat_monitor failed

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: BUBACZ Martin <martin(dot)bubacz(at)axa(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Update pg_stat_monitor failed
Date: 2026-11-06 07:18:54
Message-ID: d290bdefc66876f12af352008004e4f6b0db5464.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 2026-11-05 at 10:53 +0000, BUBACZ Martin wrote:
> I’m fairly new to postgresql and this is maybe a stupid question (sorry beforehand):
> I'm trying to install pg_stat_monitor_16-2.4.0-1PGDG.rhel9.8.x86_64 on rhel 9.8 and
> postgresql 16.9.3 and I receive the message below when updating existing version with
> "alter extension pg_stat_monitor update".
>  
> ERROR:  could not load library "/usr/pgsql-16/lib/pg_stat_monitor.so": /usr/pgsql-16/lib/pg_stat_monitor.so: undefined symbol: palloc0_mul
>  
> yum info pg_stat_monitor_16-2.4.0-1PGDG.rhel9.8.x86_64
> Last metadata expiration check: 2:21:52 ago on Thu 05 Nov 2026 08:41:50 AM CET.
> Installed Packages
> Name         : pg_stat_monitor_16
> Version      : 2.4.0
> Release      : 1PGDG.rhel9.8
> Architecture : x86_64
> Size         : 118 k
> Source       : pg_stat_monitor_16-2.4.0-1PGDG.rhel9.8.src.rpm
> Repository   : @System
> Summary      : PostgreSQL Query Performance Monitoring Tool
> URL          : https://github.com/percona/pg_stat_monitor
> License      : PostgreSQL
>  
> This version is running fine: pg_stat_monitor_16-2.2.0-1PGDG.rhel9.x86_64.rpm
>  
> Can someone advice?

palloc0_mul was introduced by commit cfb610eaa in 16.14 in a fix for CVE-2026-6473.

See the second entry in the release notes for 16.14 (https://www.postgresql.org/docs/16/release-16-14.html)
and the commit message (https://postgr.es/c/cfb610eaa)

The problem is that the pg_stat_monitor.so was built with PostgreSQL 16.14 or later,
so it references palloc0_mul, but you are trying to load it into 16.9, which does
not have that symbol yet.

You are in luck: update the PostgreSQL server to 16.latest, and the problem will
be gone.

I wish that this ABI break had been mentioned in the release notes...

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert Nabenhauer 2026-11-06 10:27:46 PostgreSQL 17: Feasibility of bounded job termination under network partitions
Previous Message Adrian Klaver 2026-11-05 16:14:48 Re: Update pg_stat_monitor failed