Re: ReadRecord wrongly assumes randAccess after 38a957316d.

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: hlinnaka(at)iki(dot)fi
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: ReadRecord wrongly assumes randAccess after 38a957316d.
Date: 2020-01-28 12:03:31
Message-ID: 20200128.210331.2278408389525245166.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Tue, 28 Jan 2020 13:12:05 +0200, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote in
> On 28/01/2020 12:44, Kyotaro Horiguchi wrote:
> > While rebasing a patch, I found that after the commit 38a957316d
> > (Sorry for overlooking that.), ReadRecord sets randAccess reverse
> > way. That is, it sets randAccess to false just after a XLogBeginRead()
> > call. The attached fixes that.
>
> Thanks, applied!

Thanks.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-01-28 12:06:06 Re: Collation versioning
Previous Message Fujii Masao 2020-01-28 11:43:33 Re: Should we add xid_current() or a int8->xid cast?