Re: PG 12.2 ERROR: cannot freeze committed xmax

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: bruno da silva <brunogiovs(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: PG 12.2 ERROR: cannot freeze committed xmax
Date: 2024-05-23 23:17:29
Message-ID: CANzqJaBfH97t21=+P1O3+QyAYoNurBgSrCP-fr=28NVNHanBGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 23, 2024 at 9:41 AM bruno da silva <brunogiovs(at)gmail(dot)com> 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message rstander 2024-05-24 00:26:15 Strange issue with unique index
Previous Message Tom Lane 2024-05-23 21:23:14 Re: expected authentication request from server, but received H