Feedback-ID: i374947ac:Fastmail
Message-ID: <1801edda-893d-4b71-8694-6d775762df8e@quadratum-braccas.com>
Date: Thu, 13 Nov 2025 10:16:54 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: vacuumdb produces ERROR: cannot freeze committed xmax
To: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-admin@lists.postgresql.org
References: <1ac45482-cf26-4d6c-b551-ce9c9a5cbeec@quadratum-braccas.com>
 <c546552f451523be94300ce788677767d867237c.camel@cybertec.at>
Content-Language: en-US
From: Sbob <sbob@quadratum-braccas.com>
In-Reply-To: <c546552f451523be94300ce788677767d867237c.camel@cybertec.at>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/1801edda-893d-4b71-8694-6d775762df8e%40quadratum-braccas.com>
Precedence: bulk


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