Re: Concurrency bug in amcheck

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Concurrency bug in amcheck
Date: 2020-04-22 15:57:00
Message-ID: 20200422155700.vvpdks2fzucwcsd3@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Peter, Just thought you might want to see this one...

On 2020-04-21 15:31:13 +0300, Alexander Korotkov wrote:
> On Tue, Apr 21, 2020 at 12:54 PM Alexander Korotkov
> <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> > I found concurrency bug in amcheck running on replica. When
> > btree_xlog_unlink_page() replays changes to replica, deleted page is
> > left with no items. But if amcheck steps on such deleted page
> > palloc_btree_page() expects it would have items.
>
> I forgot to mention that I've reproduced it on master. Quick check
> shows bug should exist since 11.

- Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jehan-Guillaume de Rorthais 2020-04-22 15:58:24 Re: [BUG] non archived WAL removed during production crash recovery
Previous Message Juan José Santamaría Flecha 2020-04-22 15:56:42 Re: PG compilation error with Visual Studio 2015/2017/2019