Message-ID: <c546552f451523be94300ce788677767d867237c.camel@cybertec.at>
Subject: Re: vacuumdb produces ERROR: cannot freeze committed xmax
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Sbob <sbob@quadratum-braccas.com>, pgsql-admin@lists.postgresql.org
Date: Thu, 13 Nov 2025 09:59:40 +0100
In-Reply-To: <1ac45482-cf26-4d6c-b551-ce9c9a5cbeec@quadratum-braccas.com>
References: <1ac45482-cf26-4d6c-b551-ce9c9a5cbeec@quadratum-braccas.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/c546552f451523be94300ce788677767d867237c.camel%40cybertec.at>
Precedence: bulk

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

That is data corruption: VACUUM encountered a tuple with a HEAP_XMAX_INVALI=
D
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 d=
atabase?
(https://postgr.es/m/0a1745be-c54d-43b9-a90f-71e4c721c17c%40quadratum-bracc=
as.com)

Perhaps it is time to restore a good backup.

Yours,
Laurenz Albe