Postgres Pro
Downloads
Home   >   mailing lists

Re: cannot freeze committed xmax - Mailing list pgsql-hackers

From Andrey M. Borodin
Subject Re: cannot freeze committed xmax
Date
Msg-id 52964780-7D6E-4EC9-AA56-EAF8239F3F19@yandex-team.ru
Whole thread Raw
In response to cannot freeze committed xmax  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: cannot freeze committed xmax
List pgsql-hackers
Tree view 

> On 20 Nov 2024, at 15:58, Andrey M. Borodin <x4mmm@yandex-team.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.

pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: per backend I/O statistics
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Add a write_to_file member to PgStat_KindInfo