Re: new heapcheck contrib module

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>,Peter Geoghegan <pg(at)bowt(dot)ie>,"Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>,Stephen Frost <sfrost(at)snowman(dot)net>,Michael Paquier <michael(at)paquier(dot)xyz>,Amul Sul <sulamul(at)gmail(dot)com>,Dilip Kumar <dilipbalaut(at)gmail(dot)com>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: new heapcheck contrib module
Date: 2020-10-26 15:27:46
Message-ID: F6071D9C-9343-4BC7-A398-295B2800E1B4@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On October 26, 2020 7:13:15 AM PDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Mon, Oct 26, 2020 at 9:56 AM Mark Dilger
>> <mark(dot)dilger(at)enterprisedb(dot)com> wrote:
>>>> hornet is still unhappy even after
>>>> 321633e17b07968e68ca5341429e2c8bbf15c331?
>
>>> That appears to be a failed test for pg_surgery rather than for
>amcheck. Or am I reading the log wrong?
>
>> Oh, yeah, you're right. I don't know why it just failed now, though:
>> there are a bunch of successful runs preceding it. But I guess it's
>> unrelated to this thread.
>
>pg_surgery's been unstable since it went in. I believe Andres is
>working on a fix.

I posted one a while ago - was planning to push a cleaned up version soon if nobody comments in the near future.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2020-10-26 15:44:15 Re: automatic analyze: readahead - add "IO read time" log message
Previous Message Stephen Frost 2020-10-26 15:02:36 Re: Internal key management system