Re: PG 12.2 ERROR: cannot freeze committed xmax

Поиск
Список
Период
Сортировка
От bruno vieira da silva
Тема Re: PG 12.2 ERROR: cannot freeze committed xmax
Дата
Msg-id CAB+Nuk_x7_8f_jKx7sHvxEYhvy6sQPFnNZ4p=BHB1_hcPsgaHw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PG 12.2 ERROR: cannot freeze committed xmax  (Ron Johnson <ronljohnsonjr@gmail.com>)
Список pgsql-general
Дерево обсуждения
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 PM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
On Thu, May 23, 2024 at 9:41 AM bruno da silva <brunogiovs@gmail.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. 


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.



--
Bruno Vieira da Silva

В списке pgsql-general по дате отправления:

Предыдущее
От: Laurenz Albe
Дата:
Сообщение: Re: Json table/column design question
Следующее
От: Andreas Joseph Krogh
Дата:
Сообщение: prevent users from SELECT-ing from pg_roles/pg_database