Update pg_stat_monitor failed
Update pg_stat_monitor failed
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.
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?
Thank you.
Regards,
martin
Martin BUBACZ
Database Administrator (Oracle)
Global Intermediate Products Oracle
Global Service Operations
AXA Group Operations
AXA Group Operations
Colonia-Allee 10-20
51067 Köln
Germany
Tel.: +49 221 148 21934
Fax: +49 221 148 44 21934
Please consider the environment before printing this e-mail. Thank you.
Planned Absence: 18.12.2026-03.01.2027
Internal
AXA Group Operations Germany GmbH
Sitz der Gesellschaft: Köln
Handelsregister: Köln HR B Nr. 22372
Geschäftsführer: Helmut Schmidt
-------------------------------------------------------------------------
Der Inhalt dieser E-Mail ist vertraulich und ausschliesslich fuer den
bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie
nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein,
so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu
setzen. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung,
Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhaltes dieser
E-Mail nicht gestattet ist.
-------------------------------------------------------------------------
This message contains confidential information and is exclusively for the
person addressed or their representative. If you are not the intended
recipient of this message and its contents, please notify the sender
immediately. Any form of unauthorised use, publication, reproduction,
copying or disclosure of the content of the e-mail is not permitted.
=========================================================================
AW: Update pg_stat_monitor failed
One additional info to below, when I check libraries in /usr/pgsql-16/lib I see that permission on pg_stat_monitor.so is set to 644 all others have 755. But even change on permission doesn’t solve the issue.
This is the Linux distro:
[root lib]# uname -a
Linux xxxx.xxxxx.xxxx 5.14.0-687.56.1.el9_8.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Oct 6 21:51:31 EDT 2026 x86_64 x86_64 x86_64 GNU/Linux
Regards,
martin
Internal
Von: BUBACZ Martin <martin.bubacz@axa.com>
Gesendet: Donnerstag, 5. November 2026 11:53
An: pgsql-general@lists.postgresql.org
Betreff: Update pg_stat_monitor failed
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.
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?
Thank you.
Regards,
martin
Martin BUBACZ
Database Administrator (Oracle)
Global Intermediate Products Oracle
Global Service Operations
AXA Group Operations
AXA Group Operations
Colonia-Allee 10-20
51067 Köln
Germany
Tel.: +49 221 148 21934
Fax: +49 221 148 44 21934
Please consider the environment before printing this e-mail. Thank you.
Planned Absence: 18.12.2026-03.01.2027
Internal
=========================================================================
AXA Group Operations Germany GmbH
Sitz der Gesellschaft: Köln
Handelsregister: Köln HR B Nr. 22372
Geschäftsführer: Helmut Schmidt
-------------------------------------------------------------------------
Der Inhalt dieser E-Mail ist vertraulich und ausschliesslich fuer den
bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie
nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein,
so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu
setzen. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung,
Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhaltes dieser
E-Mail nicht gestattet ist.
-------------------------------------------------------------------------
This message contains confidential information and is exclusively for the
person addressed or their representative. If you are not the intended
recipient of this message and its contents, please notify the sender
immediately. Any form of unauthorised use, publication, reproduction,
copying or disclosure of the content of the e-mail is not permitted.
=========================================================================
AXA Group Operations Germany GmbH
Sitz der Gesellschaft: Köln
Handelsregister: Köln HR B Nr. 22372
Geschäftsführer: Helmut Schmidt
-------------------------------------------------------------------------
Der Inhalt dieser E-Mail ist vertraulich und ausschliesslich fuer den
bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie
nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein,
so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu
setzen. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung,
Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhaltes dieser
E-Mail nicht gestattet ist.
-------------------------------------------------------------------------
This message contains confidential information and is exclusively for the
person addressed or their representative. If you are not the intended
recipient of this message and its contents, please notify the sender
immediately. Any form of unauthorised use, publication, reproduction,
copying or disclosure of the content of the e-mail is not permitted.
=========================================================================
Re: Update pg_stat_monitor failed
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
Re: Update pg_stat_monitor failed
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 > > Thank you. > > Regards, > > martin > > ** > > *Martin BUBACZ** > *Database Administrator (Oracle) -- Adrian Klaver adrian.klaver@aklaver.com
Re: Update pg_stat_monitor failed
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
Re: Update pg_stat_monitor failed
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
Re: Update pg_stat_monitor failed
You are in luck: update the PostgreSQL server to 16.latest, and the problem will
be gone.
Re: Update pg_stat_monitor failed
On Fri, 2026-11-06 at 08:39 -0500, Ron Johnson wrote: > The sad part is that (if you download the packages beforehand) it takes less than > 20 seconds to stop the instance, install RPMs and then start the instance. Why is that sad? Also, a shutdown can take a while on a busy system, unless you run a checkpoint right before you shut down. Yours, Laurenz Albe
Re: Update pg_stat_monitor failed
On Fri, 2026-11-06 at 08:39 -0500, Ron Johnson wrote:
> The sad part is that (if you download the packages beforehand) it takes less than
> 20 seconds to stop the instance, install RPMs and then start the instance.
Why is that sad?
Also, a shutdown can take a while on a busy system, unless you run a checkpoint right
before you shut down.
Re: Update pg_stat_monitor failed
On 11/6/26 5:39 AM, Ron Johnson wrote: > On Fri, Nov 6, 2026 at 2:19 AM Laurenz Albe > wrote: > [snip] > > > You are in luck: update the PostgreSQL server to 16.latest, and the > problem will > be gone. > > The sad part is that (if you download the packages beforehand) it takes > *less than 20 seconds* to stop the instance, install RPMs and then start > the instance. Or the OP could upgrade, as a stop gap measure, to pg_stat_monitor 2.3.2: https://github.com/percona/pg_stat_monitor/releases/tag/2.3.2 which was released the same day as the commit Laurenz mentioned, therefore doubtful it would contain code that conflicted. Then once they have set out and implemented an upgrade path, move on to 2.4.0. > > -- > Death to , and butter sauce. > Don't boil me, I'm still alive. > lobster! -- Adrian Klaver adrian.klaver@aklaver.com
AW: [EXTERNAL] Re: Update pg_stat_monitor failed
Thank you, Guys.
Regards,
martin
Internal
Von: Adrian Klaver <adrian.klaver@aklaver.com>
Gesendet: Samstag, 7. November 2026 16:51
An: Ron Johnson <ronljohnsonjr@gmail.com>; pgsql-general@lists.postgresql.org
Betreff: [EXTERNAL] Re: Update pg_stat_monitor failed
On 11/6/26 5: 39 AM, Ron Johnson wrote: > On Fri, Nov 6, 2026 at 2: 19 AM Laurenz Albe <laurenz. albe@ cybertec. at > <mailto: laurenz. albe@ cybertec. at>> wrote: > [snip] > > > You are in luck: update the PostgreSQL server
On 11/6/26 5:39 AM, Ron Johnson wrote: > On Fri, Nov 6, 2026 at 2:19 AM Laurenz Albe <laurenz.albe@cybertec.at > <mailto:laurenz.albe@cybertec.at>> wrote: > [snip] > > > You are in luck: update the PostgreSQL server to 16.latest, and the > problem will > be gone. > > The sad part is that (if you download the packages beforehand) it takes > *less than 20 seconds* to stop the instance, install RPMs and then start > the instance. Or the OP could upgrade, as a stop gap measure, to pg_stat_monitor 2.3.2: https://urldefense.com/v3/__https://github.com/percona/pg_stat_monitor/releases/tag/2.3.2__;!!BnkV9pdh5V0!Gn5DnuOOc0onJdap6ry_8eHQ3IEguF-DrsXE-89y5rRXbi7W6YialkJ2CPWFcbJaRUcj-1HckSMOs9ptzKx4Je5XgVk$ which was released the same day as the commit Laurenz mentioned, therefore doubtful it would contain code that conflicted. Then once they have set out and implemented an upgrade path, move on to 2.4.0. > > -- > Death to <Redacted>, and butter sauce. > Don't boil me, I'm still alive. > <Redacted> lobster! -- Adrian Klaver adrian.klaver@aklaver.com AXA Group Operations Germany GmbH
Sitz der Gesellschaft: Köln
Handelsregister: Köln HR B Nr. 22372
Geschäftsführer: Helmut Schmidt
-------------------------------------------------------------------------
Der Inhalt dieser E-Mail ist vertraulich und ausschliesslich fuer den
bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie
nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein,
so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu
setzen. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung,
Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhaltes dieser
E-Mail nicht gestattet ist.
-------------------------------------------------------------------------
This message contains confidential information and is exclusively for the
person addressed or their representative. If you are not the intended
recipient of this message and its contents, please notify the sender
immediately. Any form of unauthorised use, publication, reproduction,
copying or disclosure of the content of the e-mail is not permitted.
=========================================================================