On 11/6/26 5:39 AM, Ron Johnson wrote:
On Fri, Nov 6, 2026 at 2:19 AM Laurenz Albe <[email protected]
<mailto:[email protected]>> 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 <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
--
Adrian Klaver
[email protected]
