Re: Potential "AIO / io workers" inter-worker locking issue in PG18?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Marco Boeringa <marco(at)boeringa(dot)demon(dot)nl>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Thom Brown <thom(at)linux(dot)com>
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
Date: 2025-10-07 23:17:06
Message-ID: ut77uhgxfttgf44uc5rgxpsewbxxydraw76m4okry4hk4ek7t5@kewogxyo6ezn
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2025-10-07 19:03:40 -0400, Andres Freund wrote:
> On 2025-10-08 00:13:34 +0200, Marco Boeringa wrote:
> So somehow >60% of the CPU time is spent fetching tuples corresponding to
> index entries. That seems ... a lot. Is it possible that you have a lot of
> dead rows in the involved tables?
>
> I don't immediately see how this could be related to AIO.

Can you share the query and explain for it that was running in the "stuck"
backend?

Greetings,

Andres Freund

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2025-10-08 00:05:56 Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Previous Message Andres Freund 2025-10-07 23:03:40 Re: Potential "AIO / io workers" inter-worker locking issue in PG18?