API version mismatch error with pg_stat_monitor 2.0.0 on PostgreSQL 15.3

Description

Hi! 
pg_stat_monitor stopped working for me after upgrade from 1.1.1-2

while the monitor_version works correctly:

Steps to reproduce:
1. Open PostgreSQL
2. Run the command: select * from pg_stat_monitor;

Expected Result:

  • The query should run successfully, displaying statistics collected by the pg_stat_monitor extension.

Actual Result:

  • The query failed with the error: ERROR:  [pg_stat_monitor] pg_stat_monitor_internal: API version not supported.

  • The hint provided was: Upgrade pg_stat_monitor extension

Additional Information:

The issue appears to be a version mismatch of pg_stat_monitor extension. The version check in the code suggests that any API version less than 2.0.0 should not be supported, but the current API version is exactly 2.0.0.

Environment

  • Debian version: 11.7

  • PostgreSQL version: 15.3-1.pgdg110+1

  • Repository: http://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64

  • pg_stat_monitor version: 2.0.0
     Packages

  • Percona-pg-stat-monitor package: percona-pg-stat-monitor15 1:2.0.0-1.bullseye

Activity

Show:

Marcin Rybak May 31, 2023 at 7:16 AM

Thanks Naeem for help, I was able to solve this issue by upgrading pmm2-client to version 2.37, it wasn't available (still) in debian repo, but manually downloaded from https://www.percona.com/downloads worked as a charm. 

naeem.akhter May 29, 2023 at 3:39 PM

If you see some changes are required or missing in manuals then I would suggest you to open a ticket on PMM JIRA board

Marcin Rybak May 26, 2023 at 8:41 PM

@Naeem Akhter What do you think about that?

Marcin Rybak May 22, 2023 at 7:15 AM

Hi, I'm using PMM 2.37.0 with the pmm-admin version pmm2-client 2.35.0-6.bullseye

naeem.akhter May 22, 2023 at 2:29 AM

Which version of PMM, are you using? PMM version compatibility might be the problem. 

Done

Details

Assignee

Reporter

Components

Affects versions

Priority

Smart Checklist

Created May 16, 2023 at 1:48 PM
Updated May 31, 2023 at 7:16 AM
Resolved May 17, 2023 at 6:51 AM