Re: vacuumdb produces ERROR: cannot freeze committed xmax

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Sbob <sbob(at)quadratum-braccas(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: vacuumdb produces ERROR: cannot freeze committed xmax
Date: 2025-11-13 08:59:40
Message-ID: c546552f451523be94300ce788677767d867237c.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, 2025-11-12 at 12:10 -0700, Sbob wrote:
> running a vacuumdb is throwing this error on a PostgreSQL v15 db:
>
>
> vacuumdb: error: processing of database "prod1" failed: ERROR: cannot
> freeze committed xmax 1406773176

That is data corruption: VACUUM encountered a tuple with a HEAP_XMAX_INVALID
hint (which indicates the tuple is visible), but the deleting transaction
is committed.

Perhaps your commit log got corrupted.

Is that on the same system as you other report that indicates a corrupted database?
(https://postgr.es/m/0a1745be-c54d-43b9-a90f-71e4c721c17c%40quadratum-braccas.com)

Perhaps it is time to restore a good backup.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-admin by date

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