Re: vacuumdb produces ERROR: cannot freeze committed xmax

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: vacuumdb produces ERROR: cannot freeze committed xmax
Date: 2025-11-12 20:19:47
Message-ID: CANzqJaB+-GJgKstRLPpNj23TkwTHWNPaJj9sVrtuwN8gxFg+5A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, Nov 12, 2025 at 2:10 PM Sbob <sbob(at)quadratum-braccas(dot)com> wrote:

>
> All;
>
> running a vacuumdb is throwing this error on a PostgreSQL v15 db:
>

Which *exact* version?

> vacuumdb: error: processing of database "prod1" failed: ERROR: cannot
> freeze committed xmax 1406773176
>

What is the *exact* command?
Any other errors (like in the PG log file)?

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message CONVERS Yann - DREAL Auvergne-Rhône-Alpes/CIDDAE/SIG 2025-11-13 08:28:15 Re: pg_dump -j
Previous Message Sbob 2025-11-12 19:10:11 vacuumdb produces ERROR: cannot freeze committed xmax