Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vJVWX-009CpB-1l for pgsql-admin@arkaria.postgresql.org; Thu, 13 Nov 2025 11:29:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vJVWU-000lTE-0P for pgsql-admin@arkaria.postgresql.org; Thu, 13 Nov 2025 11:29:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vJVS0-000bYz-0O for pgsql-admin@lists.postgresql.org; Thu, 13 Nov 2025 11:25:16 +0000 Received: from mail-ot1-x333.google.com ([2607:f8b0:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vJVAR-006ty9-2I for pgsql-admin@lists.postgresql.org; Thu, 13 Nov 2025 11:07:08 +0000 Received: by mail-ot1-x333.google.com with SMTP id 46e09a7af769-7c6dca2455bso106941a34.3 for ; Thu, 13 Nov 2025 03:07:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763032027; x=1763636827; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MjrVCJGlYs3IfgE03DMzEN+8kUJ7FIyhDGVnkrcqPXE=; b=QMbsWVeInnwfAEuEDxzs/ih/Oi0S3dgzcQjNMlul+VM9oPAD62exqC/hXBRvgwbLrd iCLvUmidBkEXulJfPcqIN7xqyT0Dt+rwwXeGEczZJKBhC4laTvXB+C0heTtRaSqEXu0L CQ+iH/4vnCfMOAv41Da7DkapnHVgvA/77YpVJZjxiJCIztUlI4zI26hD3IadqaC+WkYt tRFQYxSSAFt/wUFX9smIcqrnyQfFHm2TNH+d32b60sWb+G+xrbx/vDgFQJRd8OiT4mar J5ya/vsZaygY+tFAjMWul6vrVqQ9VbCP9+rHbSf2gteFF36MyUfCAoV1bQRQj3BJ0qUY fieA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763032027; x=1763636827; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=MjrVCJGlYs3IfgE03DMzEN+8kUJ7FIyhDGVnkrcqPXE=; b=bp1WG49OJIUVIbzHUIrlENnAwXydu9KZPqROMh6tjANh3XtC1q2qACIZoKuNkPzcK3 1i8zn96MTL5ebBBmOcsZEcvAOjskuxzOW5Xp5UBGk8EUE7baDzqFTxyGaqEWYNk9AwqG Aei1P6UgB/hcAgL7h9n6gxsxfEbTgyCsEFv7ufCOgg2Ng6/bPSPIwSXsBBZw4SOuxaHu pEkAt9vBP+XasKIN89aKTugVJvqVvVI7aYpsqWVvIseRqYhc3P95fiKJNsXS4UuICoFi UkX9lI5AZ4D2H2Ho4Tnl8zX5c67aKZrjhG4z71D+YmOHmkHSPjo9EqKD59S4BaV/BOdX PjCg== X-Gm-Message-State: AOJu0Yxu2yMVuNVp7hTEhLQ5NNcIBqE2HJPBDDUJlDX4ZBEJUNZwSiTC FJrtjG2ANPEQ/mWnckyMpw7TzPoxj8NIAU6Yyw8QA+qPsZ2xxQQVk1x1qR9nVzH4G5dTHDv0J56 v5AO29MhMYzgymcRpklf1UdMfcAqaGQP4fAU5 X-Gm-Gg: ASbGnctbzmjcEZBdJrXGi+fhhJTryRWHL8uieTG87R4zb3gzqJA3BE4tAQ6x2zk8LC3 DmMzDCuzRmgbd54hH2/T4ZffdJ38Mow1NjZO3grPBtyZ2nrYbKdARcfyXqPHNZOL7mFSPVhzi+H CihbiLiKy4uQF921Q1FTWIevyZCps6vLYe1+O2c94cz6W7+57wPwLcc2DI1aNmUUHK/Oyc7XpfU ybl2jzprm9ZkH+G7K0CpOvwUvYPl+JTis4VuZyMTgi4++dxLHsJvKnykaU= X-Google-Smtp-Source: AGHT+IFVBBPeDzViTz17UOTXGcdVhnODCEYig3EGy/SNAfJxwYoTmZ+92JAKaL7oVFeOaOCQqJ+/vP9m2lI7lYmNOkw= X-Received: by 2002:a05:6870:e610:b0:3d4:b2ed:e658 with SMTP id 586e51a60fabf-3e83411d4f6mr1901357fac.7.1763032026713; Thu, 13 Nov 2025 03:07:06 -0800 (PST) MIME-Version: 1.0 References: <1ac45482-cf26-4d6c-b551-ce9c9a5cbeec@quadratum-braccas.com> In-Reply-To: <1ac45482-cf26-4d6c-b551-ce9c9a5cbeec@quadratum-braccas.com> From: Fabrice Chapuis Date: Thu, 13 Nov 2025 12:06:54 +0100 X-Gm-Features: AWmQ_bmOToSmbd-s4FaUrFhwho6BVXTUcnnTXfBGlfol78bFmxkqlGndQbvUDBQ Message-ID: Subject: Re: vacuumdb produces ERROR: cannot freeze committed xmax To: Sbob Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000ae116f064377e139" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ae116f064377e139 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, This thread could perhaps help PostgreSQL: ERROR: cannot freeze committed xmax Regards, Fabrice On Wed, Nov 12, 2025 at 8:10=E2=80=AFPM Sbob w= rote: > > All; > > 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 > > > Thanks in advance for any guidance > > > > --000000000000ae116f064377e139 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
This thread could perhaps h= elp

Regards,

Fa= brice

On Wed, Nov 12, 2025 at 8:10=E2=80= =AFPM Sbob <sbob@quadratum= -braccas.com> wrote:

All;

running a vacuumdb is throwing this error on a PostgreSQL v15 db:


vacuumdb: error: processing of database "prod1" failed: ERROR: ca= nnot
freeze committed xmax 1406773176


Thanks in advance for any guidance



--000000000000ae116f064377e139--