> 25 авг. 2020 г., в 19:36, Mark Dilger <mark.dilger@enterprisedb.com> написал(а):
Hi Mark!
Thanks for working on this important feature.
I was experimenting a bit with our internal heapcheck and found out that it's not helping with truncated CLOG anyhow.
Will your module be able to gather tid's of similar corruptions?
server/db M # select * from heap_check('pg_toast.pg_toast_4848601');
ERROR: 58P01: could not access status of transaction 636558742
DETAIL: Could not open file "pg_xact/025F": No such file or directory.
LOCATION: SlruReportIOError, slru.c:913
Time: 3439.915 ms (00:03.440)
Thanks!
Best regards, Andrey Borodin.