inconsistency between the VM page visibility status and the visibility status of the page

From: yanhui(dot)xiong <yanhui(dot)xiong(at)enmotech(dot)com>
To: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: inconsistency between the VM page visibility status and the visibility status of the page
Date: 2023-07-20 06:44:49
Message-ID: BA2423D8E34B8834+tencent_E19E17B1294A86A187B97F09@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
i had a issue here, When executing a SELECT statement using an index-only scan, i got a wrong row number because there may be an inconsistency between the VM page visibility status and the visibility status of the page,the VM bit is set and page-level is clear

i read the code and note that there has a chance to happen like this,but how it happens?
the code do clear the page-level visibility and vm bit at the same time, i don not understand how it happens

Attachment Content-Type Size
企业微信截图_5e189c3e-9c53-4bb4-97f0-1944b591070a.png application/octet-stream 164.0 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2023-07-20 07:03:32 Re: remaining sql/json patches
Previous Message Joan 2023-07-20 06:44:44 Re: There should be a way to use the force flag when restoring databases