| From: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Amul Sul <sulamul(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new heapcheck contrib module |
| Date: | 2020-08-28 05:07:45 |
| Message-ID: | 47D0EC13-0B9A-4D97-9435-0846B0DA2916@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 25 авг. 2020 г., в 19:36, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-08-28 05:33:39 | Re: SQL-standard function body |
| Previous Message | Masahiko Sawada | 2020-08-28 05:03:38 | Re: Add Information during standby recovery conflicts |