Re: [HACKERS] Suspicious place in heap_prepare_freeze_tuple() - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: [HACKERS] Suspicious place in heap_prepare_freeze_tuple()
Date
Msg-id CAD21AoBGYBaEJwhZW=wvbVmix2m9wHJhE-Kb_zTQzs-j_2nnxg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Suspicious place in heap_prepare_freeze_tuple()  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [HACKERS] Suspicious place in heap_prepare_freeze_tuple()
List pgsql-hackers
On Thu, Jul 6, 2017 at 1:36 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> Teodor Sigaev wrote:
>
>> Playing around freezing tuple I found suspicious piece of code:
>>
>> heap_prepare_freeze_tuple():
>> ...
>> frz->t_infomask = tuple->t_infomask;
>> ...
>>             frz->t_infomask &= ~HEAP_XMAX_BITS;
>>             frz->xmax = newxmax;
>>             if (flags & FRM_MARK_COMMITTED)
>>                 frz->t_infomask &= HEAP_XMAX_COMMITTED;
>>
>> Seems, in last line it should be a bitwise OR instead of AND. Now this line
>> cleans all bits in t_infomask which later will be copied directly in tuple.
>
> I think you're right.
>

I also think that's right. Should we back-patch it down to 9.3?

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Re: pg_ctl wait exit code (was Re: [COMMITTERS] pgsql:Additional tests for subtransactions in recovery)
Next
From: Tatsuo Ishii
Date:
Subject: [HACKERS] SCRAM auth and Pgpool-II