Re: vacuumdb produces ERROR: cannot freeze committed xmax

On 11/13/25 1:59 AM, Laurenz Albe wrote:
> 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)
Yes, we did a restore of the tables that seemed to be corrupted, any 
advice on determining the cause of the corruption?
>
> Perhaps it is time to restore a good backup.
>
> Yours,
> Laurenz Albe