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 1sASD8-009uZl-Nk for pgsql-general@arkaria.postgresql.org; Fri, 24 May 2024 10:31:44 +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 1sASD8-004O54-72 for pgsql-general@arkaria.postgresql.org; Fri, 24 May 2024 10:31:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sASD7-004O4w-Rg for pgsql-general@lists.postgresql.org; Fri, 24 May 2024 10:31:41 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sASD0-000Wl6-FW for pgsql-general@lists.postgresql.org; Fri, 24 May 2024 10:31:41 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-62a08438b9aso7119377b3.3 for ; Fri, 24 May 2024 03:31:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716546692; x=1717151492; 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=6dN6NpB8/42W9zgml/Q2/yxi2Vs0h00cEIgBiHvR0O0=; b=DBXUdCks+tCnakFPE9zEoxftMhSy5bmqwqFtyy6QScLFu4zzSNQOsi+JHP2lEQeMqH ZJ1F+VNpTgrvPjvQEqzOdOED9e7qX+3kiqxVIOEahSDm02rmJ2vUHP5ANfMUswuGEVM2 +3dfXqhGaHAcZaITDwfRll3kMAeTZEeAvxFfn5pU9v70U3aCpqokqKAULK9AnxMXRBMm /68FPXxfWBhjIufv9F2erGqU17EWocjrZRDcSsvGiU4G9scUfDBjB4IwmAFthM3UjW+b 9cO3BFOT3e2VgEtrT2Pvpfkbyao6Vls/hKpO+7kqBZSIlEv4KU/IL7oXkMP47m21l2nc nMvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716546692; x=1717151492; 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=6dN6NpB8/42W9zgml/Q2/yxi2Vs0h00cEIgBiHvR0O0=; b=j0QlwPzDX8aBl+ADNbw6C289a4dCZy1lnVv6uJyf0L09GM/odvAsShb2+kzQq1DTof Cs4sOWRZ/JXtdxpH3zDhe36vaIaqVnd/20zxCZ6I2QoQ7+38obn3k4sJ2Jsy67DOQzcT zpJCo4A6Jr6p3J0B2AUprW3V1FOoTCFOuQy8BgIba4fBuGsTIkmfWsPq/NIFmZJGgrQA j1/gx9cZDqCF0eaJLEoyaIUzwxhPQao82FnpIjMW66CD/0x7wrLVMmQ2TycePO3tMi8D TMnHb9v6ypDAfmsFwNLBqWmsLtptROChd1xhFdW2rXxsskfbNbA8EiyC3csd48EGGQ1y jxJw== X-Gm-Message-State: AOJu0YzLI9vUOTARCeh1bZjU37sUkJorty3Gjo94klih+AAksYJ13YdG RJuicLMQl/y7ZerBBX+gervU/yaOnTlDPNZLZW3vqhvX7GaR40bhaLXx6/TtdlH6JKr/8BPjG3k pyompcdugMUCeLCuboTqOqVX/auM= X-Google-Smtp-Source: AGHT+IE+wtDSXMRgMqUcdEzHR9rHgHvuOh0WiKqh4ohtwxZ6JNRSmhVyfVDLuDqzhlezkDKnYbXDXgNqmD8fAbuQG74= X-Received: by 2002:a0d:eb4d:0:b0:627:df3b:74b7 with SMTP id 00721157ae682-62a08b3a5a0mr16715737b3.0.1716546690976; Fri, 24 May 2024 03:31:30 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: bruno vieira da silva Date: Fri, 24 May 2024 06:31:18 -0400 Message-ID: Subject: Re: PG 12.2 ERROR: cannot freeze committed xmax To: Ron Johnson Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000c194e6061930ab29" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c194e6061930ab29 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Ron. I did find one bug fix commit mentioning this error but it was saying that was due to the interaction of two other commits that at least the first one was after the cut of pg 12.2. so I have dismissed that as my deployment issue. I was looking for more evidence to push for a pg minor upgrade, the issue is for my context any upgrades requires a big test effort. so I was looking for more solid evidence. On Thu, May 23, 2024 at 7:17=E2=80=AFPM Ron Johnson wrote: > 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. > > --=20 Bruno Vieira da Silva --000000000000c194e6061930ab29 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Ron.

I did find one bug fix comm= it mentioning this error but it was saying that was due to the interaction = of two other commits that at least the first one was after the cut of pg 12= .2. so I have dismissed=C2=A0that as my deployment issue.

I was looking for more evidence to push for a pg minor upgrade, the= issue is for my context any upgrades requires a big test effort. so I was = looking for more solid evidence.


On Thu, May 23, 2024= at 7:17=E2=80=AFPM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
On Thu, May 23= , 2024 at 9:41=E2=80=AFAM bruno da silva <brunogiovs@gmail.com> wrote:
=
Hello,
I have a deployment with PG 12.2 reporting=C2= =A0ERROR: cannot freeze committed xmax
using Red Hat Enterprise Linux 8.9.

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

You're missing four years=C2=A0of bug fixes.=C2=A0<= /div>

Could this error be caused by OS/Hardware related issues?<= /div>

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



--
Bruno Vieira da Silva
--000000000000c194e6061930ab29--