vacuumdb produces ERROR: cannot freeze committed xmax

From:	Sbob <sbob(at)quadratum-braccas(dot)com>
To:	pgsql-admin(at)lists(dot)postgresql(dot)org
Subject:	vacuumdb produces ERROR: cannot freeze committed xmax
Date:	2025-11-12 19:10:11
Message-ID:	1ac45482-cf26-4d6c-b551-ce9c9a5cbeec@quadratum-braccas.com
Views:	Whole Thread | Raw Message | Download mbox | Resend email
Thread:	2025-11-12 19:10:11 from Sbob <sbob(at)quadratum-braccas(dot)com>  2025-11-12 20:19:47 from Ron Johnson <ronljohnsonjr(at)gmail(dot)com>  2025-11-13 08:59:40 from Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>   2025-11-13 17:16:54 from Sbob <sbob(at)quadratum-braccas(dot)com>    2025-11-13 18:29:59 from Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>  2025-11-13 11:06:54 from Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
Lists:	pgsql-admin

Responses

• Re: vacuumdb produces ERROR: cannot freeze committed xmax at 2025-11-12 20:19:47 from Ron Johnson
• Re: vacuumdb produces ERROR: cannot freeze committed xmax at 2025-11-13 08:59:40 from Laurenz Albe
• Re: vacuumdb produces ERROR: cannot freeze committed xmax at 2025-11-13 11:06:54 from Fabrice Chapuis

Browse pgsql-admin by date

	From	Date	Subject
Next Message	Ron Johnson	2025-11-12 20:19:47	Re: vacuumdb produces ERROR: cannot freeze committed xmax
Previous Message	Sbob	2025-11-12 19:08:37	Re: vacuum process running for more than 2 days, still in scanning heap phase