Re: ReadRecord wrongly assumes randAccess after 38a957316d.

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: ReadRecord wrongly assumes randAccess after 38a957316d.
Date: 2020-01-28 11:12:05
Message-ID: c798a91a-dd4e-242e-7623-35e561003b17@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2020-01-28 11:27:15 Re: Autovacuum on partitioned table
Previous Message Daniel Gustafsson 2020-01-28 10:57:19 Re: Some incorrect option sizes for PQconninfoOption in libpq