> 28 авг. 2020 г., в 18:58, Robert Haas <robertmh...@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 (while toast was accessible until CLOG truncation). Best regards, Andrey Borodin.
- Re: new heapcheck contrib module Robert Haas
- Re: new heapcheck contrib module Peter Geoghegan
- Re: new heapcheck contrib module Robert Haas
- Re: new heapcheck contrib module Peter Geoghegan
- Re: new heapcheck contrib module Robert Haas
- Re: new heapcheck contrib module Amul Sul
- Re: new heapcheck contrib module Amul Sul
- Re: new heapcheck contrib module Amul Sul
- Re: new heapcheck contrib module Andrey M. Borodin
- Re: new heapcheck contrib module Robert Haas
- Re: new heapcheck contrib modu... Andrey M. Borodin
- Re: new heapcheck contrib ... Mark Dilger
- Re: new heapcheck contrib ... Robert Haas
- Re: new heapcheck contrib ... Andrey M. Borodin
- Re: new heapcheck contrib ... Mark Dilger
- Re: new heapcheck contrib ... Peter Geoghegan
- Re: new heapcheck contrib module Mark Dilger
- Re: new heapcheck contrib module Robert Haas
- Re: new heapcheck contrib module Mark Dilger
- Re: new heapcheck contrib modu... Peter Geoghegan
- Re: new heapcheck contrib modu... Robert Haas