Re: cannot freeze committed xmax

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cannot freeze committed xmax
Date: 2024-11-20 14:39:44
Message-ID: 52964780-7D6E-4EC9-AA56-EAF8239F3F19@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Nov 2024, at 15:58, Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> PFA the patch doing so.

Ugh. The patch is simply dysfunctional, sorry. xmax_status is being checked uninitiated.
But, well, it highlights the idea: make verify_heapam() aware of such corruptions.
What do you think?

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2024-11-20 14:45:55 Re: Add a write_to_file member to PgStat_KindInfo
Previous Message Bertrand Drouvot 2024-11-20 14:20:18 Re: per backend I/O statistics