Re: vacuumdb produces ERROR: cannot freeze committed xmax - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: vacuumdb produces ERROR: cannot freeze committed xmax
Date
Msg-id ed38b33f0bc5548b50426df91f91b0d961fb0f0b.camel@cybertec.at
Whole thread Raw
In response to Re: vacuumdb produces ERROR: cannot freeze committed xmax  (Sbob <sbob@quadratum-braccas.com>)
List pgsql-admin
On Thu, 2025-11-13 at 10:16 -0700, Sbob wrote:
> Yes, we did a restore of the tables that seemed to be corrupted, any
> advice on determining the cause of the corruption?

Investigate what odd things you did with the database.

In my experience, the main causes for corruption are:

- shoddy or old hardware

- bad administration (e.g., badly taken backups)

- software bugs

Yours,
Laurenz Albe



pgsql-admin by date:

Previous
From: Sbob
Date:
Subject: Re: vacuumdb produces ERROR: cannot freeze committed xmax
Next
From: ek ek
Date:
Subject: rebuild big tables with pgrepack