Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?) - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)
Date
Msg-id CAPpHfdtGcDF38Y9pLP_w3h54eN3tpuFw1Xw15grNFgZStaUJLw@mail.gmail.com
Whole thread Raw
In response to Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On Thu, Feb 27, 2025 at 12:24 AM Peter Geoghegan <pg@bowt.ie> wrote:
>
> On Wed, Feb 26, 2025 at 5:16 PM Tomas Vondra <tomas@vondra.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



pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: vacuumdb changes for stats import/export
Next
From: vignesh C
Date:
Subject: Re: Add -k/--link option to pg_combinebackup