pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: BUBACZ Martin <martin.bubacz@axa.com>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Update pg_stat_monitor failed
Date: Thu, 5 Nov 2026 08:14:48 -0800
Message-ID: <c814f502-b77f-4623-91e9-cce14cda9174@aklaver.com> (raw)
In-Reply-To: <a6423120-dd38-465f-b01e-39d89d85e96b@aklaver.com>
References: <ZR6PR04MB642637BFC6B399FBFC3FDC271CE3772@ZR6PR04MB642637.eurprd04.prod.outlook.com>
	<a6423120-dd38-465f-b01e-39d89d85e96b@aklaver.com>

On 11/5/26 8:03 AM, Adrian Klaver wrote:
> On 11/5/26 2:53 AM, BUBACZ Martin wrote:
>> Hi,
>>
>> 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.
>>
> 
>>
>> This version is running fine: 
>> pg_stat_monitor_16-2.2.0-1PGDG.rhel9.x86_64.rpm
>>
>> Can someone advice?
> 
> Since the problem occurred with the pg_stat_monitor version change I 
> would suggest filing an issue here:
> 
> https://github.com/percona/pg_stat_monitor/issues

Especially given the below.

2.4.0
Release highlights

"This release is focused on the stability and reliability of 
pg_stat_monitor. Large parts of the internals were reworked to remove 
long-standing sources of crashes, memory leaks and incorrect statistics, 
and the test suite was extended with test cases backported from 
pg_stat_statements so that the behavior of both extensions can be 
compared directly."

Add to that Ron's observation of the Postgres version being well back 
from current and I think there is good case to be made for a bad 
interaction between new code and old code.

> 
>>
>> Thank you.
>>
>> Regards,
>>
>> martin
>>
>> **
>>
>> *Martin BUBACZ**
>> *Database Administrator (Oracle)


-- 
Adrian Klaver
adrian.klaver@aklaver.com






view thread (9+ messages)  latest in thread

Message-ID: <c814f502-b77f-4623-91e9-cce14cda9174@aklaver.com>
Permalink:  ../c814f502-b77f-4623-91e9-cce14cda9174@aklaver.com/
Also on:    postgresql.org/message-id/c814f502-b77f-4623-91e9-cce14cda9174@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, martin.bubacz@axa.com
  Subject: Re: Update pg_stat_monitor failed
  In-Reply-To: <c814f502-b77f-4623-91e9-cce14cda9174@aklaver.com>
  References: <ZR6PR04MB642637BFC6B399FBFC3FDC271CE3772@ZR6PR04MB642637.eurprd04.prod.outlook.com> <a6423120-dd38-465f-b01e-39d89d85e96b@aklaver.com> <c814f502-b77f-4623-91e9-cce14cda9174@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox