ReadRecord wrongly assumes randAccess after 38a957316d.

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: ReadRecord wrongly assumes randAccess after 38a957316d.
Date: 2020-01-28 10:44:08
Message-ID: 20200128.194408.2260703306774646445.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello.

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.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
0001-Fix-randAccess-setting-in-ReadRecrod.patch text/x-patch 1.2 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2020-01-28 10:57:19 Re: Some incorrect option sizes for PQconninfoOption in libpq
Previous Message Daniel Gustafsson 2020-01-28 10:29:39 Re: Setting min/max TLS protocol in clientside libpq