# Why does pg\_stat\_monitor trigger a PostgreSQL restart? **URL:** \ **Category:** PMM 3.x\ **Created:** [December 26, 2025, 11:36am UTC](https://forums.percona.com/t/why-does-pg-stat-monitor-trigger-a-postgresql-restart/39942 "2025-12-26T11:36:23Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ANDiv1976](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/andiv1976/32/20170_2.png) [@ANDiv1976](https://forums.percona.com/u/ANDiv1976)\ **Post date:** [December 26, 2025, 11:36am UTC](https://forums.percona.com/t/why-does-pg-stat-monitor-trigger-a-postgresql-restart/39942/1 "2025-12-26T11:36:23Z")
PostgreSQL version 14.17, PMM 3.4.1., pg\_stat\_monitor 2.2 The server has 32GB RAM, 28% allocated for huge pages, shared\_buffers size is 25%. The PostgreSQL logs contain the following entries: `received immediate shutdown request` `[pg_stat_monitor] pgsm_shmem_shutdown: Shutdown initiated.` pg\_stat\_monitor settings: `pg_stat_monitor.pgsm_enable_overflow: true` `pg_stat_monitor.pgsm_enable_pgsm_query_id: true` `pg_stat_monitor.pgsm_enable_query_plan: true` `pg_stat_monitor.pgsm_histogram_max: 30000` `pg_stat_monitor.pgsm_histogram_min: 50` `pg_stat_monitor.pgsm_max: 256` `pg_stat_monitor.pgsm_max_buckets: 20` `pg_stat_monitor.pgsm_normalized_query: true` `pg_stat_monitor.pgsm_query_shared_buffer: 192` `pg_stat_monitor.pgsm_track_application_names: false` `pg_stat_monitor.pgsm_track_planning: false` This is a serious bug. We caught it in the test environment. ---
**Author:** ![ANDiv1976](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/andiv1976/32/20170_2.png) [@ANDiv1976](https://forums.percona.com/u/ANDiv1976)\ **Post date:** [December 30, 2025, 5:08am UTC](https://forums.percona.com/t/why-does-pg-stat-monitor-trigger-a-postgresql-restart/39942/2 "2025-12-30T05:08:30Z")
the topic can be deleted. the problem is solved. The initiator of the reboot is not pg\_stat\_monitor. But the last message from him is such that it initiates the restart of the posgres ---
**Author:** ![Evgeniy\_Patlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/evgeniy_patlan/32/41_2.png) [@Evgeniy\_Patlan](https://forums.percona.com/u/Evgeniy_Patlan)\ **Post date:** [December 30, 2025, 6:14pm UTC](https://forums.percona.com/t/why-does-pg-stat-monitor-trigger-a-postgresql-restart/39942/3 "2025-12-30T18:14:28Z")
Hey @ANDiv1976 I would suggest creating jira ticket for such improvement ---
**Author:** ![ANDiv1976](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/andiv1976/32/20170_2.png) [@ANDiv1976](https://forums.percona.com/u/ANDiv1976)\ **Post date:** [January 3, 2026, 9:37am UTC](https://forums.percona.com/t/why-does-pg-stat-monitor-trigger-a-postgresql-restart/39942/4 "2026-01-03T09:37:09Z")
Hey @Evgeniy_Patlan The initiator of the restart was Patroni, since it lost connection to the etcd server. However, PostgreSQL’s pg\_stat\_monitor left the following log entry: `received immediate shutdown request` `[pg_stat_monitor] pgsm_shmem_shutdown: Shutdown initiated.` This makes it appear as if pg\_stat\_monitor initiated the PostgreSQL restart, which is misleading. It would be good to fix this! ---
**Author:** ![chang\_junye](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/chang_junye/32/22752_2.png) [@chang\_junye](https://forums.percona.com/u/chang_junye)\ **Post date:** [January 6, 2026, 3:14am UTC](https://forums.percona.com/t/why-does-pg-stat-monitor-trigger-a-postgresql-restart/39942/5 "2026-01-06T03:14:24Z")
i encounterd same problem, how to fix it? ---
**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 29, 2026, 3:05pm UTC](https://forums.percona.com/t/why-does-pg-stat-monitor-trigger-a-postgresql-restart/39942/6 "2026-04-29T15:05:46Z")
Hi, Encountered this issue today. Is this still open? 2026-04-29 15:19:12.916 IST,13498,69e00cc7.34ba,7,2026-04-16 03:40:15 IST,0,LOG,00000,“received fast shutdown request”,“”,“postmaster”,0 2026-04-29 15:19:13.284 IST,13501,69e00cc8.34bd,1306,2026-04-16 03:40:16 IST,0,LOG,00000,“checkpoint starting: shutdown immediate”,“”,“checkpointer”,“received fast shutdown request”,“”,“postmaster”, “[pg\_stat\_monitor] pgsm\_shmem\_shutdown: Shutdown initiated.” ---
**Author:** ![Agustin\_G](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/agustin_g/32/14111_2.png) [@Agustin\_G](https://forums.percona.com/u/Agustin_G)\ **Post date:** [May 9, 2026, 9:28pm UTC](https://forums.percona.com/t/why-does-pg-stat-monitor-trigger-a-postgresql-restart/39942/7 "2026-05-09T21:28:00Z")
Hi @chang_junye and @harish.jaipu , If you are also using Patroni, you can check Patroni logs with: ```auto sudo journalctl -u patroni ``` Otherwise, you’ll need to investigate who sent that shutdown signal: ```auto received fast shutdown request ``` Check OS logs and dmesg outputs, too, just in case.