Re: ReadRecord wrongly assumes randAccess after 38a957316d. - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: ReadRecord wrongly assumes randAccess after 38a957316d.
Date
Msg-id c798a91a-dd4e-242e-7623-35e561003b17@iki.fi
Whole thread Raw
In response to ReadRecord wrongly assumes randAccess after 38a957316d.  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: ReadRecord wrongly assumes randAccess after 38a957316d.  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
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!

- Heikki



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Some incorrect option sizes for PQconninfoOption in libpq
Next
From: Masahiko Sawada
Date:
Subject: Re: Autovacuum on partitioned table