Re: new heapcheck contrib module - Mailing list pgsql-hackers

From Andrey M. Borodin
Subject Re: new heapcheck contrib module
Date
Msg-id 773B38BD-E27F-4C49-8678-B316261C9189@yandex-team.ru
Whole thread Raw
In response to Re: new heapcheck contrib module  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: new heapcheck contrib module  (Mark Dilger <mark.dilger@enterprisedb.com>)
Re: new heapcheck contrib module  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers

> 28 авг. 2020 г., в 18:58, Robert Haas <robertmhaas@gmail.com> написал(а):
> In the case
> you mention, I think we should view that as a problem with clog rather
> than a problem with the table, and thus out of scope.

I don't think so. ISTM It's the same problem of xmax<relfrozenxid actually, just hidden behind detoasing.
Our regular heap_check was checking xmin\xmax invariants for tables, but failed to recognise the problem in toast
(whiletoast was accessible until CLOG truncation). 

Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Anastasia Lubennikova
Date:
Subject: Re: MultiXact\SLRU buffers configuration
Next
From: Mark Dilger
Date:
Subject: Re: new heapcheck contrib module