Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Subject: Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)
Date: 2025-02-26 22:13:14
Message-ID: CAH2-Wz=qnw+Htr5i8MFrwd=Q0cxAPDAFTV4+mpRfu1WsVT0K9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 26, 2025 at 5:09 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> So, it's stuck in AdvanceXLInsertBuffer ... interesting. Another
> interesting fact is it's testing 75dfde13639, which is just a couple
> commits after 6a2275b895:

> which reworked AdvanceXLInsertBuffer() quite a bit, it seems. OTOH the
> last (successful) run on widorbird was on eaf502747b, which already
> includes 6a2275b895, so maybe it's unrelated.

Are you aware that Alexander reverted this only a day later, in commit 3fb58625?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-02-26 22:16:13 Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)
Previous Message Tomas Vondra 2025-02-26 22:08:57 suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)