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 18:29:59
Message-ID: ed38b33f0bc5548b50426df91f91b0d961fb0f0b.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message ek ek 2025-11-14 19:14:34 rebuild big tables with pgrepack
Previous Message Sbob 2025-11-13 17:16:54 Re: vacuumdb produces ERROR: cannot freeze committed xmax