Re: pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum

From: Andres Freund <andres(at)anarazel(dot)de>
To: Daniel Shelepanov <deniel1495(at)mail(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum
Date: 2022-02-18 16:56:37
Message-ID: 20220218165637.lp7ar3ana2xirsuc@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2022-02-18 00:09:48 +0300, Daniel Shelepanov wrote:
> I've been examining a floating bug in pg_visibility. To reproduce it, you
> have to:
>
> 1) apply a patch to pg_visibility's tests (you can find it attached)
>
> 2) run test-icx.sh (attached) from the root of the postgresql's source tree

Could you try to minimize the script? A 300 line reproducer is quite long. And
it looks like it won't even work in non postgres-pro tree.

One thing to do would be to modify pg_visibility to elog(PANIC, "something")
when it encounters corruption. Then you would have a chance of inspecting the
state of the tuple/page in that moment.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2022-02-18 17:51:19 Re: pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum
Previous Message Satish Nayak [NMC - IT] 2022-02-18 16:19:00 Re: BUG #17410: After upgrade to postgresql 12.9 from 12.6 , some of the statements having ”=” operator not returnin