# Disable sending messages to the client side

**URL:** <https://forums.percona.com/t/disable-sending-messages-to-the-client-side/39698>\
**Category:** PMM 3.x\
**Created:** [November 7, 2025, 1:39pm UTC](https://forums.percona.com/t/disable-sending-messages-to-the-client-side/39698 "2025-11-07T13:39:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**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:** [November 7, 2025, 1:39pm UTC](https://forums.percona.com/t/disable-sending-messages-to-the-client-side/39698/1 "2025-11-07T13:39:17Z")

</div>

How can I disable sending unnecessary messages from pg\_stat\_monitor to the client side? We configured pg\_stat\_monitor.pgsm\_max to limit shared memory consumption. And if the buffer doesn’t free up in time, the following message is generated:

WARNING: [pg\_stat\_monitor] pgsm\_store: Hash table is out of memory and can no longer store queries!  
DETAIL: You may reset the view or when the buckets are deallocated, pg\_stat\_monitor will resume saving queries. Alternatively, try increasing the value of pg\_stat\_monitor.pgsm\_max.

And these messages are being sent to the client side. Sending such messages is not needed by the client.

---

<div class="post-metadata">

**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:** [November 11, 2025, 9:51pm UTC](https://forums.percona.com/t/disable-sending-messages-to-the-client-side/39698/2 "2025-11-11T21:51:20Z")

</div>

Hi @ANDiv1976 ,

You could try setting a higher lever for client\_min\_messages, but this will of course mean you may be missing on some other (more important) messages.

These shouldn’t be too verbose, since they should be firing only once per out of memory occurrence:

> <https://github.com/percona/pg_stat_monitor/blob/release-2.3.0/pg_stat_monitor.c#L1988>

Is it firing too much either way?

---

<div class="post-metadata">

**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:** [November 14, 2025, 12:49pm UTC](https://forums.percona.com/t/disable-sending-messages-to-the-client-side/39698/3 "2025-11-14T12:49:16Z")

</div>

Under high load, starting from approximately 8,000 TPS, queries disappear in QAN and errors appear in the logs. Until I limited the memory usage with `pg_stat_monitor.pgsm_max`, PostgreSQL was restarting.