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.94.2) (envelope-from ) id 1sAHgv-008jgm-N7 for pgsql-general@arkaria.postgresql.org; Thu, 23 May 2024 23:17:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sAHgu-00HPQT-Ct for pgsql-general@arkaria.postgresql.org; Thu, 23 May 2024 23:17:44 +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.94.2) (envelope-from ) id 1sAHgu-00HPQL-1z for pgsql-general@lists.postgresql.org; Thu, 23 May 2024 23:17:44 +0000 Received: from mail-ot1-x329.google.com ([2607:f8b0:4864:20::329]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sAHgr-001gqA-Ey for pgsql-general@lists.postgresql.org; Thu, 23 May 2024 23:17:42 +0000 Received: by mail-ot1-x329.google.com with SMTP id 46e09a7af769-6f0ecec6411so4557798a34.1 for ; Thu, 23 May 2024 16:17:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716506261; x=1717111061; 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=PnF2s5TDKfUp7QiW6xxVvfBS9aPGdYMEfsJr2hEPlN4=; b=Cs+k+JYql7+i5K5qNuJcwso5Yz7ev66Jz78yY8k2n7lLlV75FUUvxy8/qDzeGCj9Dv GN+EsEUGZKf3gr3BtRHoia9xIsrfHKL6HMgeK3tNIixUPfZAi2KogcPp2VbXewCZV1dp ITXcOog968ZQYHyqZfBSVUGjw11qOtEP1s32JfDyRLMu6CzDfRPBUfGvbs9Af7dZJtuf SBysSZATazkPDWbYfp5Qx/MhkdA9UK0x0h6ZsktnKU8foXNk6pMfGH8Un+gw75w3Z8RK RIJeHqfaRszdVfFz+453/o76kDcN6/jXkn/JcWUB8HhueYRo0PQFNITyphp0hm62nimI 4auQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716506261; x=1717111061; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PnF2s5TDKfUp7QiW6xxVvfBS9aPGdYMEfsJr2hEPlN4=; b=AOoif8F2q5nfMX/9AR4NibCEToND2SOX9y6a2RJPJaxAJdyoz7EDSX5UyKg3YBcUJz taIbmSe3eiQ21vFli9g9wlg/VF4Sr8Wm3aNF8Ipg1ye4hftyeqvaY2xhqF96eUqKlUNJ uy5s/nXpjx+7lv5nvzCLqPrGJphmKapzUh+e/h3hhTuL6Fz+lMBs16ekCrM6/GKrOyu6 6TZunChBLoFEZsxd8b/47Fb2FD/zUW/J9Mvpv7tNVmQ3Q4K7NwJ3ki5hJJqFvUMRmHB4 +yHlnTpXrhzQFGhYuByd4KmYuUfTbk/6prSX0n59RZjqCQ8QM2gYCFMhnvxn5n6yYtXj dzLw== X-Gm-Message-State: AOJu0YztyaSkm62x1afnG5RB7BjK0+Sls0ivuzY7sU3+8b6V8GTchM4Z y7N0bjIVXRcqlT+teDkWBNS81oyD5Y3WFgg3X24nP1Bn7r7go3ilrgjxFr7CRIX+VEFxuHBlJlk wcH+9MpbAoxg1g5MUi+ET9GTMxx4= X-Google-Smtp-Source: AGHT+IGfrbWRkpvmlK+o8f51CqmYKIoYAuZIZdQppuoycoqajTS+wNXDOcW2/VtU9L07GPuPmorwzicxdYLcpFVew6k= X-Received: by 2002:a05:6870:b6a3:b0:24c:5cd6:6401 with SMTP id 586e51a60fabf-24ca11d1daamr849429fac.13.1716506260625; Thu, 23 May 2024 16:17:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Thu, 23 May 2024 19:17:29 -0400 Message-ID: Subject: Re: PG 12.2 ERROR: cannot freeze committed xmax To: bruno da silva Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000eb635d0619274124" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000eb635d0619274124 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, May 23, 2024 at 9:41=E2=80=AFAM bruno da silva wrote: > Hello, > I have a deployment with PG 12.2 reporting ERROR: cannot freeze committed > xmax > using Red Hat Enterprise Linux 8.9. > > What is the recommended to find any bug fixes that the version 12.2 had > that could have caused this error. > https://www.postgresql.org/docs/release/ You're missing *four years* of bug fixes. Could this error be caused by OS/Hardware related issues? > Four years of bug fixes is more likely the answer. --000000000000eb635d0619274124 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, May 23, 2024 at 9:41=E2=80=AFAM b= runo da silva <brunogiovs@gmail.= com> wrote:
Hello,
I have a deployme= nt with PG 12.2 reporting=C2=A0ERROR: ca= nnot freeze committed xmax
using Red Hat Enterprise Li= nux 8.9.

What is the recommended=C2=A0to find any = bug fixes that the version 12.2 had that could have caused this error.=C2= =A0

https://www.postgresql.org/docs/release/
<= /div>

You're missing four years=C2=A0of bug f= ixes.=C2=A0

Could this error be caused by OS/Hardware rela= ted issues?

=C2=A0Four years of= bug fixes is more likely the answer.

--000000000000eb635d0619274124--