Re: contrib/pg_visibility craps out in assert-enabled builds - Mailing list pgsql-hackers

From Tom Lane
Subject Re: contrib/pg_visibility craps out in assert-enabled builds
Date
Msg-id 10788.1475523189@sss.pgh.pa.us
Whole thread Raw
In response to Re: contrib/pg_visibility craps out in assert-enabled builds  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Sep 30, 2016 at 10:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> The problem seems to be that HeapTupleSatisfiesVacuum asserts
>> Assert(ItemPointerIsValid(&htup->t_self));
>> while collect_corrupt_items hasn't bothered to set up the t_self
>> field of the HeapTupleData it's passing in.  This would imply that
>> you never tested this code in an assert-enabled build, which I find
>> surprising.  Am I missing something?

> My standard build script uses --enable-cassert, so I doubt that's the
> case.  It's more likely that on my system it just happened to find
> some non-zero garbage at that point on the stack that made it not fail
> the assertion.

Yeah, after I looked closer at what the Assert is actually testing,
I realized it was just blind luck that I'd managed to see it fail.
It's a pretty weak test :-(.  Anyway, fixed now.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Vitaly Burovoy
Date:
Subject: Re: Proposal: ON UPDATE REMOVE foreign key action
Next
From: Kevin Grittner
Date:
Subject: Re: [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.