Re: [HACKERS] WAL consistency check facility - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] WAL consistency check facility
Date
Msg-id CA+TgmoYSejRvJHLudPx81OkjMbr0AxUhx9HdoVq86c79bAy=og@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] WAL consistency check facility  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Tue, Feb 7, 2017 at 6:32 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> On Tue, Jan 31, 2017 at 9:36 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>>
>> +            if (!HeapTupleHeaderXminFrozen(page_htup))
>> +                page_htup->t_infomask |= HEAP_XACT_MASK;
>> +            else
>> +                page_htup->t_infomask |= HEAP_XMAX_COMMITTED |
>> HEAP_XMAX_INVALID;
>>
>> Comment doesn't address this logic.  Also, the "else" case shouldn't
>> exist at all, I think.
>>
>
> In the *if* check, it just checks frozen status of xmin, so I think
> you need to mask xmax related bits in else check.  Can you explain
> what makes you think that the else case shouldn't exist?

Oh, you're right.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Beena Emerson
Date:
Subject: Re: [HACKERS] Proposal : For Auto-Prewarm.
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] 0/NULL/NIL assignments in build_*_rel()