# Pg\_stat\_monitor 2.1.0 - Segmentation fault **URL:** \ **Category:** pg\_stat\_monitor\ **Tags:** percona, postgres\ **Created:** [January 21, 2025, 9:52am UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247 "2025-01-21T09:52:22Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![shigaev.s](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@shigaev.s](https://forums.percona.com/u/shigaev.s)\ **Post date:** [January 21, 2025, 9:52am UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/1 "2025-01-21T09:52:22Z")
Hello! There is a PostgreSQL 15.4 cluster with Patroni. Installed packages: ```auto percona-haproxy/unknown,now 2:2.8.1-1.jammy amd64 [installed, can be upgraded to: 2:2.8.11-1.jammy] percona-patroni/unknown,now 1:3.1.0-1.jammy all [installed, can be upgraded to: 1:4.0.3-1.jammy] percona-pg-stat-monitor15/unknown,now 1:2.0.1-3.jammy amd64 [installed, can be upgraded to: 1:2.1.0-1.jammy] percona-pgbackrest/unknown,now 1:2.47-1.jammy amd64 [installed, can be upgraded to: 1:2.54.0-1.jammy] percona-postgresql-15-pgaudit/unknown,now 1:1.7.0-6.jammy amd64 [installed, can be upgraded to: 1:1.7.0-8.jammy] percona-postgresql-15-repack/unknown,now 1:1.4.8-3.jammy amd64 [installed, can be upgraded to: 1:1.5.1-1.jammy] percona-postgresql-15-wal2json/unknown,now 1:2.5-5.jammy amd64 [installed, can be upgraded to: 1:2.6-2.jammy] percona-postgresql-15/unknown,now 2:15.4-1.jammy amd64 [installed, can be upgraded to: 2:15.10-1.jammy] percona-postgresql-client-15/unknown,now 2:15.4-1.jammy amd64 [installed, can be upgraded to: 2:15.10-1.jammy] percona-postgresql-common/unknown,now 1:252-1.jammy all [installed, can be upgraded to: 1:266-1.jammy] percona-postgresql-contrib/unknown,now 1:252-1.jammy all [installed, can be upgraded to: 1:266-1.jammy] percona-ppg-server-15/unknown,now 1:15.4-1.jammy amd64 [installed, can be upgraded to: 1:15.10-1.jammy] percona-ppg-server-ha-15/unknown,now 1:15.4-1.jammy amd64 [installed, can be upgraded to: 1:15.10-1.jammy] percona-release/unknown,now 1.0-27.generic all [installed, can be upgraded to: 1.0-29.generic] ``` I upgraded the percona-pg-stat-monitor15 package to version 2.1.0 and after restarting PostgreSQL. checked the extension version: ```sql postgres=# SELECT pg_stat_monitor_version(); pg_stat_monitor_version ------------------------- 2.1.0 (1 line) ``` After this, errors and failures in PostgreSQL began, leading to a restart and recovery. Log: ```auto 2025-01-21 12:28:02 "2025-01-21 12:28:02.365 MSK PID:[10814] TR:[0] postgres@postgres/[n/a] SQLSTATE:[57P03] "IMPORTANT: Database system in recovery mode 2025-01-21 12:28:01 "2025-01-21 12:28:01.688 MSK PID:[10809] TR:[0] @/ SQLSTATE:[00000] "HINT: If this happens repeatedly, some data may have been corrupted and you should select an earlier point to restore to. 2025-01-21 12:28:01 "2025-01-21 12:28:01.688 MSK PID:[10809] TR:[0] @/ SQLSTATE:[00000] "MESSAGE: The DB system was interrupted during recovery, log time: 2025-01-21 12:10:07 MSK 2025-01-21 12:28:00 "2025-01-21 12:28:00.454 MSK PID:[1693] TR:[0] @/ SQLSTATE:[00000] "MESSAGE: [pg_stat_monitor] pgsm_shmem_shutdown: Shutdown initiated. 2025-01-21 12:28:00 "2025-01-21 12:28:00.451 MSK PID:[1693] TR:[0] @/ SQLSTATE:[00000] "MESSAGE: All server processes terminated... reinitializing 2025-01-21 12:28:00 "2025-01-21 12:28:00.001 MSK PID:[10808] TR:[0] pmm@postgres/[n/a] SQLSTATE:[57P03] "IMPORTANT: Database system in recovery mode 2025-01-21 12:28:00 "2025-01-21 12:27:59.995 MSK PID:[1693] TR:[0] @/ SQLSTATE:[00000] "MESSAGE: Terminating all remaining active server processes 2025-01-21 12:28:00 "2025-01-21 12:27:59.995 MSK PID:[1693] TR:[0] @/ SQLSTATE:[00000] "DETAILS: The process that terminated was executing the action: SELECT /* agent='pgstatmonitor' */ "pg_stat_monitor"."bucket", "pg_stat_monitor"."client_ip", "pg_stat_monitor"."query", "pg_stat_monitor"."calls", "pg_stat_monitor"."shared_blks_hit", "pg_stat_monitor"."shared_blks_read", "pg_stat_monitor"."shared_blks_dirtied", "pg_stat_monitor"."shared_blks_written", "pg_stat_monitor"."local_blks_hit", "pg_stat_monitor"."local_blks_read", "pg_stat_monitor"."local_blks_dirtied", "pg_stat_monitor"."local_blks_written", "pg_stat_monitor"."temp_blks_read", "pg_stat_monitor"."temp_blks_written", "pg_stat_monitor"."blk_read_time", "pg_stat_monitor"."blk_write_time", "pg_stat_monitor"."resp_calls", "pg_stat_monitor"."cpu_user_time", "pg_stat_monitor"."cpu_sys_time", "pg_stat_monitor"."rows", "pg_stat_monitor"."relations", "pg_stat_monitor"."datname", "pg_stat_monitor"."userid", "pg_stat_monitor"."top_queryid", "pg_stat_monitor"."planid", "pg_stat_monitor"."query_plan", "pg_stat_monitor"."top_query", "pg_stat_monitor"."application_name", "pg_stat_monitor"."cmd_type", "pg_stat_mon 2025-01-21 12:28:00 "2025-01-21 12:27:59.995 MSK PID:[1693] TR:[0] @/ SQLSTATE:[00000] "MESSAGE: The server process (PID 10806) was terminated by signal 11: Segmentation fault ``` The recovery process begins and everything starts all over again. Finally installed the old release: ```bash apt-get install percona-pg-stat-monitor15=1:2.0.1-3.jammy ``` Restarted PostgreSQL and checked the extension version: ```sql postgres=# SELECT pg_stat_monitor_version(); pg_stat_monitor_version ------------------------- 2.0.1 (1 line) ``` What is the problem? Is it safe to update to 2.1.0? ---
**Author:** ![shigaev.s](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@shigaev.s](https://forums.percona.com/u/shigaev.s)\ **Post date:** [January 24, 2025, 12:47pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/2 "2025-01-24T12:47:54Z")
Has anyone encountered this problem? How to solve it? ---
**Author:** ![Arda\_Beyazoglu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/arda_beyazoglu/32/1156_2.png) [@Arda\_Beyazoglu](https://forums.percona.com/u/Arda_Beyazoglu)\ **Post date:** [February 7, 2025, 3:08pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/3 "2025-02-07T15:08:55Z")
I have the same problem since yesterday with postgres 15.10. A minor package upgrade caused this i think. ---
**Author:** ![shigaev.s](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@shigaev.s](https://forums.percona.com/u/shigaev.s)\ **Post date:** [February 7, 2025, 3:16pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/4 "2025-02-07T15:16:28Z")
Did you manage to solve it or did you also have to roll back the version? ---
**Author:** ![Arda\_Beyazoglu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/arda_beyazoglu/32/1156_2.png) [@Arda\_Beyazoglu](https://forums.percona.com/u/Arda_Beyazoglu)\ **Post date:** [February 7, 2025, 3:18pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/5 "2025-02-07T15:18:16Z")
No, no not yet. Still same issue. As soon as i touch pg\_stat\_monitor in a query, postgres crashes. ---
**Author:** ![Arda\_Beyazoglu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/arda_beyazoglu/32/1156_2.png) [@Arda\_Beyazoglu](https://forums.percona.com/u/Arda_Beyazoglu)\ **Post date:** [February 7, 2025, 3:23pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/6 "2025-02-07T15:23:23Z")
I solved it. After the upgrade, extension must be manually updated to latest version after connecting to postgres. ALTER EXTENSION pg\_stat\_monitor UPDATE TO “2.1”; Running this command and restarting again, i dont have problems anymore. ---
**Author:** ![shigaev.s](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@shigaev.s](https://forums.percona.com/u/shigaev.s)\ **Post date:** [February 7, 2025, 3:26pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/7 "2025-02-07T15:26:04Z")
Even if there was a restart of PostgreSQL and when checking the version it shows 2.1 loaded? ---
**Author:** ![Arda\_Beyazoglu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/arda_beyazoglu/32/1156_2.png) [@Arda\_Beyazoglu](https://forums.percona.com/u/Arda_Beyazoglu)\ **Post date:** [February 7, 2025, 3:28pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/8 "2025-02-07T15:28:30Z")
Well i forgot to check the version using sql. My case might be different than yours. But you should upgrade to latest and then run that update query to see yourself first, i think. ---
**Author:** ![harish.jaipu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/harish.jaipu/32/20282_2.png) [@harish.jaipu](https://forums.percona.com/u/harish.jaipu)\ **Post date:** [April 17, 2025, 10:31am UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/9 "2025-04-17T10:31:49Z")
This issue still appears even after giving upgrade. Recently we got a crash ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/9/5/959553d0d63e79d83877a45106d2ec860036ac26.png) ---
**Author:** ![shigaev.s](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@shigaev.s](https://forums.percona.com/u/shigaev.s)\ **Post date:** [April 17, 2025, 11:53am UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/10 "2025-04-17T11:53:48Z")
Interesting. I recently did a clean installation of PostgreSQL 15.11 and pg\_stat\_monitor 2.1.0, and didn’t notice any problems. ---
**Author:** ![Mohan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mohan/32/19798_2.png) [@Mohan](https://forums.percona.com/u/Mohan)\ **Post date:** [April 17, 2025, 12:43pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/11 "2025-04-17T12:43:23Z")
The Postgres version used here is 16.8 which has the pg\_stat\_monitor version 2.1.0 had the above issue. ---
**Author:** ![shigaev.s](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@shigaev.s](https://forums.percona.com/u/shigaev.s)\ **Post date:** [April 17, 2025, 2:52pm UTC](https://forums.percona.com/t/pg-stat-monitor-2-1-0-segmentation-fault/36247/12 "2025-04-17T14:52:01Z")
It looks like this is a bug.