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

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)
Date: 2025-02-27 09:45:32
Message-ID: CAPpHfdtGcDF38Y9pLP_w3h54eN3tpuFw1Xw15grNFgZStaUJLw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 27, 2025 at 12:24 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> On Wed, Feb 26, 2025 at 5:16 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> > Oh, I forgot about that. I guess if the theory is the commit might be
> > causing this, and it's been already reverted, I should just restart the
> > instance, so that it tests with the revert.
>
> According to the revert commit's commit message there was also
> problems on batta at the time. Might have been the same issue that you
> saw on widowbird. Alexander?

Yes, the backtrace posted by Tomas from widowbird looks quite the same
as posted by Michael from batta. My apologies for committing not
well-tested patch.

------
Regards,
Alexander Korotkov
Supabase

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2025-02-27 09:49:58 Re: Add -k/--link option to pg_combinebackup
Previous Message John Naylor 2025-02-27 09:36:04 Re: vacuumdb changes for stats import/export