Re: Update pg_stat_monitor failed

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Update pg_stat_monitor failed
Date: 2026-11-06 13:39:31
Message-ID: CANzqJaC42kpkxLmTUN4nitNncTDHRw0bWMtdXVv6PH1y3b8rTg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Nov 6, 2026 at 2:19 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
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.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2026-11-07 08:25:14 Re: Update pg_stat_monitor failed
Previous Message Robert Nabenhauer 2026-11-06 10:27:46 PostgreSQL 17: Feasibility of bounded job termination under network partitions