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 1vJHK0-00HD1P-1n for pgsql-admin@arkaria.postgresql.org; Wed, 12 Nov 2025 20:20:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vJHJx-00EIan-0Z for pgsql-admin@arkaria.postgresql.org; Wed, 12 Nov 2025 20:20:01 +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 1vJHJw-00EIaf-2d for pgsql-admin@lists.postgresql.org; Wed, 12 Nov 2025 20:20:00 +0000 Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vJHJv-006mwn-0x for pgsql-admin@lists.postgresql.org; Wed, 12 Nov 2025 20:19:59 +0000 Received: by mail-oi1-x231.google.com with SMTP id 5614622812f47-450136c3e05so11984b6e.3 for ; Wed, 12 Nov 2025 12:19:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762978798; x=1763583598; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=WZNpgaFaefVuvi6CGN7PTi1PhypR6S6HhcGqfA31KjU=; b=BsCy3Rt+hGn7KrvJuMho2voXwciy7pM0/SLwMu/Ri5124x+sG6KthiJdVduKzB5XGK AJkPVTWntZa98+dNCEPwA22kd0vaBGuB+tY/8QJPzWYoEE0zZMAUmLBN7Y+iYAY0kkZT dLjgwSwnPgijQ2+Vwx4YkfAxw3+xHjjcanyBB6vJgkPWAMj/upEYQzE7pG3DUJ0vyMlH b9YmcWNkHjfKI3ghO6iW6wB4EGJ2oQTQ5OC9cw+JcITX1dzN4G1MI8xSUNZvw+t8SEm2 0ci7vCVmhbkRSvMdITH1R0hy1JlLSd9BLXeHACA21G/6T1Xk226sFVByrJbYIRSAJW3u MvLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762978798; x=1763583598; h=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=WZNpgaFaefVuvi6CGN7PTi1PhypR6S6HhcGqfA31KjU=; b=meTanqxRJ2C7gPQQHKJHn7i6xl1LOtf5kqxUEvwx4OpNQs6tFSd0Cy0gg3J67sY7Gj 78yv6RHXtRQl6rUnCjFiNBdtbhqTsGD2KCJng1k0zLv4zeg6q9ADj3Enxz0RFVKymOLP N60Z/qmqPbTokJTUpG+ef/WVUscHBKepAO4FGg76/wlMoDZSyA5zw7qDloAbcKFiWox6 uS9ceZrtspKK3H8bmdAgPiGyFGPDExgY6kAW0ean+4cMXBIMuf1aMkzNXKn9GZlj3D9E PjFrT7nIJzeFJj4QQ6cI99rjQheSNqYchUa7uXKwjFo8Mbs4FX0gum/8YtFTndiN2iun h4Ow== X-Gm-Message-State: AOJu0Ywkw0ySAJVjI5E2lqb7ejfrMbkcjtXln8L/iESI+u+YdM3ZkM6D mD8iDlv1E2Pjup4EcFT/icSb+D+7dfFo8BgjQz6ZJHSZeyYXyHcLrEt8wFMt9TtPS9G+rBfrZOd 7tMZvOzjK9xZCV9dFmhn+JaPQRxRYosdTFQ== X-Gm-Gg: ASbGnctO7qWfWBCSewUyxMl39DBpM0mOFMVZ/iJl2l2tmXwmiZ0Ikmix0+uDWfBWkhb fKttaz2a9b0ODJVzcm/RTF2nmWew7+sANIdxOgeWLaeNS+NLOpvu1gr4rqPcFe6IiffL+qe0kNz 6eBSqsmXrLK39fJhUf/xCOwxkHYuVmtbislJ3TuEuecO6kdX9ZeA+1dZkrfajUgHxKNFEukA9Uh 2k8vgsrf1f4uyJl/JlWqk610lwC2Va45xhm2uGMgtkVBoqqQlRseGht3ywIEQ== X-Google-Smtp-Source: AGHT+IHd/7OAdpTm3R+GvSHWGz17Sfnye88yCjpeAwjjI2aT31/YvzyoTvq3Gj0AUnwUvu2f0Dr6tT/zoRu4wB5iNlU= X-Received: by 2002:a05:6808:178b:b0:441:8f74:fc1 with SMTP id 5614622812f47-450745cc9b3mr2034519b6e.62.1762978798187; Wed, 12 Nov 2025 12:19:58 -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: Ron Johnson Date: Wed, 12 Nov 2025 15:19:47 -0500 X-Gm-Features: AWmQ_bnK7hzKxMncqyn3dCYrvxoPkmmOA2rSr7J2xVmm0WoYk1nHe2nFSIY62KA Message-ID: Subject: Re: vacuumdb produces ERROR: cannot freeze committed xmax To: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000003388e06436b7d1d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000003388e06436b7d1d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 12, 2025 at 2:10=E2=80=AFPM Sbob w= rote: > > All; > > running a vacuumdb is throwing this error on a PostgreSQL v15 db: > Which *exact* version? > vacuumdb: error: processing of database "prod1" failed: ERROR: cannot > freeze committed xmax 1406773176 > What is the *exact* command? Any other errors (like in the PG log file)? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000003388e06436b7d1d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Nov 12, 2025 at 2:10=E2=80=AFPM S= bob <sbob@quadratum-bracca= s.com> wrote:
=

All;

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

Which exact=C2=A0version?
=C2= =A0
vacuumdb: error:= processing of database "prod1" failed: ERROR: cannot
freeze committed xmax 1406773176

What i= s the exact=C2=A0command?
Any other errors (like in the PG= log file)?

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'= m still alive.
<Redacted> lobster!
--00000000000003388e06436b7d1d--